react-architecture
Trigger: React component architecture, composition, boundaries. Preserve and evolve React component APIs.
- License 许可
- Apache-2.0
- 最近更新
- 2026-07-30
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- react-architecture
- license
- Apache-2.0
- metadata
- { "author": "LuHer18", "version": "1.0" }
- description
- Trigger: React component architecture, composition, boundaries. Preserve and evolve React component APIs.
03 SKILL.md 正文
Activation Contract
Use for React component APIs, composition, module placement, and client/server or framework boundary decisions. Inspect repository architecture, tooling, detected versions, and matching official documentation before proposing version-specific behavior.
Hard Rules
Preserve established architecture and dependencies; ask before changing either. Keep render logic pure, compose small public interfaces, and update inputs explicitly. Do not invent framework APIs, server behavior, or runtime boundaries when evidence is absent.
Decision Gates
Identify the existing component boundary, ownership of public APIs, detected framework/runtime, and whether a client/server boundary exists. If evidence is incomplete, state the assumption or ask. Follow the matching framework documentation for framework-owned behavior.
Execution Steps
Map the current module and component APIs before moving code. Prefer composition over new coupling. Keep rendering deterministic, isolate external synchronization outside render, and make boundary data explicit. Verify behavior-verifiable tests using existing project tools after each observable contract change.
Output Contract
Report preserved architecture, affected component interfaces, framework boundary evidence, assumptions, and observable checks. Name proposed dependency or architecture changes separately for approval. Do not claim an API or version that repository evidence and official documentation do not establish.
References
No bundled references; verify matching official docs before API-specific work.
04 同仓库更多 Skills
spring-boot
Build Spring Boot services with explicit boundaries and tests.
sap-ui5
Build SAP UI5 applications with maintainable controllers and views.
react-testing
Trigger: React tests, UI behavior, async interaction. Prove user-visible React behavior with existing tools.
react-state-data-integration
Trigger: React state, forms, async data, integration. Clarify state and data ownership without coupling layers.
react-quality-safeguards
Trigger: React accessibility, security, privacy, performance, observability. Apply evidence-based production safeguards.
nodejs
Build Node.js applications with portable, testable runtime boundaries.