메뉴
Use when the task asks about EPDC Site Factory architecture, repository boundaries, documentation ownership, Codex standardization, or which directories to inspect before changing the deterministic pipeline.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | factory-repository-map |
| description | Use when the task asks about EPDC Site Factory architecture, repository boundaries, documentation ownership, Codex standardization, or which directories to inspect before changing the deterministic pipeline. |
README.md, AGENTS.md, and docs/codex-knowledge-architecture.md.docs/architecture/README.md for the cross-repository system map before reading subsystem documents..agents/skills/ for Codex-native reusable workflowsagents/ for agent contractsprompts/ for planning-prompt guidanceexecution-prompts/ for runtime-facing promptsruntime/ for post-factory execution documentationassembler/ for deterministic assemblyblueprints/ and starters/ for reusable implementation assetsskills/ as legacy migration history only. The active repo-scoped skills live under .agents/skills/.Use when implementing an EPDC Blueprint project from a visual design concept, especially references under blueprints/dentist/concepts/. This skill teaches Codex to extract visual language, section rhythm, spacing, typography, CTA placement, and responsive intent from a concept artifact while preserving the Factory architecture, Astro implementation target, Blueprint component hierarchy, and project-owned src/data content model.
Use when a task involves EPDC frontend implementation planning or execution in Astro and TypeScript, including route structure, layouts, shared components, page composition, project bootstrap, or static-first frontend decisions.
Use when a task involves EPDC content planning or execution, including page hierarchy, messaging structure, CTA placement, service-page organization, local-business content, or multilingual content requirements.
Use when a task involves transforming an EPDC specification into structured implementation tasks, including category assignment, dependency ordering, priority selection, and acceptance-criteria coverage.
Use when a task involves EPDC validation or review work, including specification coverage, functional checks, responsive review, accessibility review, SEO verification, release readiness, and structured findings.
Use when a task involves EPDC SEO planning or execution, including metadata, local SEO, sitemap coverage, robots rules, structured data, page-intent alignment, or crawlability requirements.