メニュー
Create or modify a reusable component that survives latency, cancellation, and partial failure (progress modal, upload widget, job panel), handling every backend state with all six interaction states rendered.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
MANUAL skill covering the full atlas lifecycle outside of task work: onboard (scaffold the docs/ SSOT plus .atlas/ internal state, inventory skills, recommend what to run next), install (verify and wire claude-mem, context-mode, hooks, project config), connectors (guided vendor MCP connector setup across domain plugins), and repair (fix a broken atlas install: marketplace, rollbacks, hooks, assets). Run with no args for onboarding plus recommendations; run with --fix to auto-repair.
Atlas architect: boot the workspace. Verify claude-mem and context-mode, scan the project, recommend tooling (confirm first), wire hooks, seed the docs/ SSOT.
This skill should be used when the user asks to "audit my codebase against The Pragmatic Programmer", run a "pragmatic audit", "check what pragmatic principles are implemented", "review codebase for pragmatic practices", "find what's missing from the pragmatic programmer in this project", or wants a structured review of a codebase/project/monorepo against the book's principles, tips, and practices. Produces a ranked report of what is implemented, partially implemented, and missing, each finding cited to the book concept and to file:line evidence. Supports --chapters to scope dimensions and --report to set output path.
This skill should be used when the user is "designing a module", "deciding an architecture", "debugging a bug", "refactoring code", "writing tests", "naming things", "handling concurrency", "decoupling components", "choosing inheritance vs composition", "adding error handling", asks "what does The Pragmatic Programmer say about X", "is this DRY", "should I use inheritance or composition", "how should I structure this", or otherwise wants the relevant Pragmatic Programmer principles, tips, or practices surfaced for the work in progress. Surfaces 1-4 relevant principles with book tip numbers and citations to the concept files.
Read-only database audit via parallel subagents: inventory a live schema, reconcile it against the code, and check privileges and naming before any change.
Reproducible bug, exception, stack trace, or bad output: root-cause fix with evidence, not a patch over. Use when you want the actual cause fixed, not the symptom hidden.
| name | atlas-component |
| description | Create or modify a reusable component that survives latency, cancellation, and partial failure (progress modal, upload widget, job panel), handling every backend state with all six interaction states rendered. |
| when_to_use | build a reusable component that handles latency, cancellation, and partial failure - progress modal, upload widget, or job panel |
| allowed-tools | Read, Glob, Grep, Bash, Edit, MultiEdit |
| paths | ["components/**","**/*.tsx"] |
| argument-hint | [component name+purpose] [props contract] [backend contract] |
Apply the Operating Contract to this entire task. It is injected below.
cat "${CLAUDE_PLUGIN_ROOT}/references/operating-contract.md"
If the contract did not load above, read ${CLAUDE_PLUGIN_ROOT}/references/operating-contract.md and apply it before proceeding.
Read ${CLAUDE_SKILL_DIR}/references/component-pattern.md and follow the props, className, six-state, and file-pattern contract it defines. Seed a new file from ${CLAUDE_SKILL_DIR}/templates/component.seed.tsx when starting from scratch.
atlas-componentBuild the single reusable component described in $ARGUMENTS, defining its contract first and proving every state renders.
Inputs to read from $ARGUMENTS: the component (name and purpose), the props contract (props with types), and the backend contract it consumes (endpoints, payload shape, polling vs stream, cancel semantics). If a required input is missing or ambiguous, ask once for it, then proceed.