메뉴
Pointer to the spec-structure standards file. Read this before writing or editing any implementation spec.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | spec-structure |
| description | Pointer to the spec-structure standards file. Read this before writing or editing any implementation spec. |
Read .pi/agent-docs/standards/spec-structure.md for this project's spec
layout rules.
If that file does not exist yet, run /sync-project-harness to port it from
the base harness, or create it manually from the template at:
~/.pi/agent/skills/agent-os/spec-structure/template.md
Use this skill when the user wants to save, update, or reference visual design assets for the project. Triggers on "save design", "update designs", "sync designs", "add visual", "design assets", "claude design export", "design folder", "/design". Also fires proactively when the agent is about to write UI code (React components, CSS, Tailwind classes, layout) — in that case, read the active design first so code matches the visual spec. The design folder is always at `.pi/design/` and the agent should always check it before writing any UI-facing code.
Pointer to the jsdoc-conventions standards file. Read this before writing or editing any JSDoc in a project.
Port new paradigms from the global base harness (~/.pi/agent/) into the current project's .pi/ harness, adapting them to match the project's stack, workflow tier, and conventions. Run in any project to pull in improvements made to another project's harness.
Break down a spec.md or requirements.md into an actionable tasks.md with strategic grouping and ordering. Used after spec creation and before implementation.
Detect the project type from code signals and reorganize standards folders to match — web app, backend API, CLI, library, dotfiles, mobile, or monorepo.
Extract tribal knowledge and recurring patterns from the codebase into concise, documented standards files in agent-os/standards/.
