메뉴
Validates software engineering documentation separation between OSE Platform style guides (docs/explanation/) and AyoKoding educational content (apps/ayokoding-www/). Ensures no duplication, proper prerequisite statements, and style guide focus on repository-specific conventions only.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
AI agent development standards including frontmatter structure, naming conventions, tool access patterns, model selection, and reference documentation structure
UI development skill covering design token usage, shadcn/ui + Radix composition patterns, accessibility requirements, anti-patterns catalog, and brand context for OrganicLever and OSE Platform. Auto-loads when working on TSX components, CSS, or UI design tasks.
Comprehensive project planning standards for plans/ directory including folder structure (ideas/, backlog/, in-progress/, done/), stage-aware naming convention (done uses YYYY-MM-DD__identifier/; backlog and in-progress use identifier/ with no date prefix), five-document file organization (README.md, brd.md, prd.md, tech-docs.md, delivery.md for multi-file default; single README.md for trivially-small single-file exception), BRD/PRD content-placement rules, Gherkin acceptance criteria, and the mandatory structured multiple-choice grilling gates (pre-write and post-write) for resolving design decisions with the user. Essential for creating structured, executable project plans.
Workflow pattern standards for creating multi-agent orchestrations including YAML frontmatter (name, goal, termination, inputs, outputs), execution phases (sequential/parallel/conditional), agent coordination patterns, and Gherkin success criteria. Essential for defining reusable, validated workflow processes.
Trunk Based Development workflow - all development on main branch with small frequent commits, minimal branching, and continuous integration. Covers when branches are justified (exceptional cases only), commit patterns, feature flag usage for incomplete work, environment branch rules (deployment only), and AI agent default behavior (the repo-wide default delivery mode is `worktree-to-pr` -- a short-lived plan branch in a disposable worktree pushed to a draft PR; direct push to main remains available as an explicit selection). Essential for understanding repository git workflow and keeping branches short-lived
Common software development workflow patterns shared across all language developer agents
| name | docs-validating-software-engineering-separation |
| description | Validates software engineering documentation separation between OSE Platform style guides (docs/explanation/) and AyoKoding educational content (apps/ayokoding-www/). Ensures no duplication, proper prerequisite statements, and style guide focus on repository-specific conventions only. |
| created | "2026-02-07T00:00:00.000Z" |
This Skill provides comprehensive guidance for validating the separation between repository-specific style guides (docs/explanation/software-engineering/) and educational content (apps/ayokoding-www/), as defined in the Programming Language Documentation Separation Convention.
Use this Skill when:
CRITICAL: Only validate relationships explicitly listed in the Software Design Reference prerequisite table.
Authoritative Source: Software Design Reference - Specific Prerequisites
Current explicit relationships to validate:
DO NOT validate languages/frameworks not in this table (TypeScript, Python, etc.) until they are explicitly added to the Software Design Reference.
CRITICAL: docs/explanation/ content MUST NOT duplicate AyoKoding educational content.
Separation Pattern:
See Programming Language Documentation Separation Convention for complete rules.
Validate Software Design Reference table:
Only validate entries explicitly in this table - do not check other languages/frameworks.
For each docs/explanation path in the table:
For each docs/explanation path in the table:
FAIL patterns:
PASS patterns:
For each AyoKoding path in the table:
For each relationship in the table:
# Read Software Design Reference
# Extract "Specific Prerequisites" table
# Parse table rows to get:
# - docs/explanation paths
# - ayokoding-web paths
# Store as validation scope (ONLY validate these)
For each row in the prerequisite table:
FAIL (docs/explanation/.../golang/):
## Variables in Go
Go variables can be declared multiple ways:
var x int = 10
y := 20
Why: Teaching Go syntax (belongs in AyoKoding)
PASS (docs/explanation/.../golang/):
**Prerequisite**: Complete [AyoKoding Golang](...)
## Variable Naming in OSE Platform
- Domain entities: ZakatPayment, WaqfDonation
- Repository variables: zakatRepo, waqfRepo
Why: OSE Platform naming conventions (not syntax tutorial)
FAIL:
# Java
Java is used for...
## Best Practices
Why: No prerequisite statement
PASS:
# Java
## Prerequisite Knowledge
**REQUIRED**: Complete [AyoKoding Java learning path](...)
These are OSE Platform-specific style guides, not educational tutorials.
CRITICAL:
HIGH:
MEDIUM:
LOW:
Primary: Programming Language Documentation Separation Convention
Supporting: