Agent skill
atomic-page
Create a React PAGE that binds templates/organisms to real app data and routing. Use for route-level components. Pages handle data loading, orchestration, and side effects.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/atomic-page
SKILL.md
Atomic Design: PAGE (React Functional Components)
You are creating a PAGE: a route-level component that binds UI to real data and app concerns.
Hard rules
- Functional components only.
- Orchestration lives here:
- Data fetching (via the project’s standard: loaders, query libs, server components, etc.)
- Side effects (analytics, navigation, subscriptions) in
useEffector framework equivalents
- Keep UI reusable:
- Prefer pushing rendering into templates/organisms; keep pages thin.
- Error/loading states:
- Must have consistent handling aligned with the repo’s conventions.
- Performance:
- Avoid waterfall fetching; colocate queries where the project expects.
- Memoize expensive derived data with
useMemowhen justified.
Output expectations
- Provide:
Page.tsxPage.test.tsx(routing + async states, if applicable)- A brief note explaining which layer owns which responsibility (page vs template vs organism).
Recommended folder conventions
src/pages/<PageName>/...(or framework equivalent)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?