Technical Content Marketing

Skill Profile

(Select at least one profile to enable specific modules)

• [ ] DevOps
• [x] Backend
• [ ] Frontend
• [ ] AI-RAG
• [ ] Security Critical

Overview

This skill provides comprehensive guidance and best practices for implementation. It enables teams to achieve reliable, maintainable, and scalable solutions.

When to use / When NOT to use

• ✅ Use when: Implementing this capability in your project
• ✅ Use when: Need to follow established patterns and conventions
• ❌ Avoid when: The requirements don't match this skill's scope
• ❌ Avoid when: Simpler alternatives would suffice

Why This Matters

• Reduces Technical Debt: Following established patterns prevents costly rework
• Increases System Stability: Proper implementation reduces bugs and downtime
• Improves Team Velocity: Clear guidance helps teams work more efficiently
• Reduces Maintenance Costs: Well-structured code is easier to maintain
• Ensures Investment Confidence: Following standards gives confidence in technical decisions

Core Concepts & Rules

1. Core Principles

• Follow established patterns and conventions
• Maintain consistency across codebase
• Document decisions and trade-offs

2. Implementation Guidelines

• Start with the simplest viable solution
• Iterate based on feedback and requirements
• Test thoroughly before deployment

Inputs / Outputs / Contracts

• Inputs:
  • Requirements and specifications
  • Existing codebase and architecture
  • Team context and constraints
• Entry Conditions:
  • Project repository initialized
  • Development environment set up
  • Required dependencies installed
• Outputs:
  • Implementation code and documentation
  • Test cases and test results
  • Deployment artifacts
• Artifacts Required (Deliverables):
  • Source code changes
  • Updated documentation
  • Test coverage reports
• Acceptance Evidence:
  • All tests passing
  • Code review approved
  • Documentation updated
• Success Criteria:
  • Meets all functional requirements
  • Follows established patterns
  • Test coverage ≥ 80%

Skill Composition

• Depends on: None
• Compatible with: None
• Conflicts with: None
• Related Skills: None

Technical Content Marketing

Quick Start

Assumptions / Constraints / Non-goals

• Assumptions:
  • Development environment is properly configured
  • Required dependencies are available
  • Team has basic understanding of domain
• Constraints:
  • Must follow existing codebase conventions
  • Time and resource limitations
  • Compatibility requirements
• Non-goals:
  • This skill does not cover edge cases outside scope
  • Not a replacement for formal training

Compatibility & Prerequisites

• Supported Versions:
  • Python 3.8+
  • Node.js 16+
  • Modern browsers (Chrome, Firefox, Safari, Edge)
• Required AI Tools:
  • Code editor (VS Code recommended)
  • Testing framework appropriate for language
  • Version control (Git)
• Dependencies:
  • Language-specific package manager
  • Build tools
  • Testing libraries
• Environment Setup:
  • .env.example keys: API_KEY, DATABASE_URL (no values)

Test Scenario Matrix (QA Strategy)

| Type | Focus Area | Required Scenarios / Mocks | | :--- | :--- | :--- | | Unit | Core Logic | Must cover primary logic and at least 3 edge/error cases. Target minimum 80% coverage | | Integration | DB / API | All external API calls or database connections must be mocked during unit tests | | E2E | User Journey | Critical user flows to test | | Performance | Latency / Load | Benchmark requirements | | Security | Vuln / Auth | SAST/DAST or dependency audit | | Frontend | UX / A11y | Accessibility checklist (WCAG), Performance Budget (Lighthouse score) |

Technical Guardrails & Security Threat Model

1. Security & Privacy (Threat Model)

• Top Threats: Injection attacks, authentication bypass, data exposure

• [ ] Data Handling: Sanitize all user inputs to prevent Injection attacks. Never log raw PII
• [ ] Secrets Management: No hardcoded API keys. Use Env Vars/Secrets Manager
• [ ] Authorization: Validate user permissions before state changes

2. Performance & Resources

• [ ] Execution Efficiency: Consider time complexity for algorithms
• [ ] Memory Management: Use streams/pagination for large data
• [ ] Resource Cleanup: Close DB connections/file handlers in finally blocks

3. Architecture & Scalability

• [ ] Design Pattern: Follow SOLID principles, use Dependency Injection
• [ ] Modularity: Decouple logic from UI/Frameworks

4. Observability & Reliability

• [ ] Logging Standards: Structured JSON, include trace IDs request_id
• [ ] Metrics: Track error_rate, latency, queue_depth
• [ ] Error Handling: Standardized error codes, no bare except
• [ ] Observability Artifacts:
  • Log Fields: timestamp, level, message, request_id
  • Metrics: request_count, error_count, response_time
  • Dashboards/Alerts: High Error Rate > 5%

Agent Directives & Error Recovery

(ข้อกำหนดสำหรับ AI Agent ในการคิดและแก้ปัญหาเมื่อเกิดข้อผิดพลาด)

• Thinking Process: Analyze root cause before fixing. Do not brute-force.
• Fallback Strategy: Stop after 3 failed test attempts. Output root cause and ask for human intervention/clarification.
• Self-Review: Check against Guardrails & Anti-patterns before finalizing.
• Output Constraints: Output ONLY the modified code block. Do not explain unless asked.

Definition of Done (DoD) Checklist

• [ ] Tests passed + coverage met
• [ ] Lint/Typecheck passed
• [ ] Logging/Metrics/Trace implemented
• [ ] Security checks passed
• [ ] Documentation/Changelog updated
• [ ] Accessibility/Performance requirements met (if frontend)

Anti-patterns

Reference Links & Examples

• Internal documentation and examples
• Official documentation and best practices
• Community resources and discussions

Versioning & Changelog

• Version: 1.0.0
• Changelog:
  • 2026-02-22: Initial version with complete template structure