القائمة
Use when making non-trivial changes, modifying public APIs, or proposing new framework features. Use when changes affect multiple files or require design decisions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when adding new API surface, modifying existing APIs, or defining TypeScript types for framework features. Use when discussing method signatures, return types, decorator APIs, or module exports.
Use when discussing, expanding, or designing any subsystem in SPEC.md. Use when user asks about goals, API shape, edge cases, or configuration for HTTP, Router, ORM, Queue, Mail, Views, or other framework subsystems.
Use when adding new files, patterns, or examples to skeleton/. Use when creating new controller, model, job, mailable, migration, view, or component in the skeleton app.
Use when designing new subsystem, comparing implementation approaches, or user asks how other frameworks handle something. Use when researching Laravel, Rails, AdonisJS, Inertia.js, or similar framework patterns.
Use after any change to skeleton/, packages/core/, or docs/. Use to verify types compile and documentation is synchronized.
| name | kubit-proposing-change |
| description | Use when making non-trivial changes, modifying public APIs, or proposing new framework features. Use when changes affect multiple files or require design decisions. |
Non-trivial changes require synchronized updates across types, spec, skeleton, and docs. Major changes need an RFC.
Create RFC in docs/rfcs/ when:
Skip RFC for:
Create docs/rfcs/YYYY-MM-DD-slug.md:
# RFC: [Title]
## Summary
One paragraph overview.
## Motivation
Why is this needed? What problem does it solve?
## Public API Changes
TypeScript signatures for new/changed APIs.
## Example Usage
How it looks in skeleton/.
## Implementation Notes
Key considerations for future implementation.
## Alternatives Considered
What else was considered and why rejected.
## Test Plan
How to verify this works (mapped to skeleton/tests/).
## Required Updates
- [ ] packages/core/*.d.ts
- [ ] docs/SPEC.md
- [ ] skeleton/*
- [ ] CLAUDE.md (if docs changed)
Any API change requires ALL of these:
| File | Update |
|---|---|
skeleton/* | Usage example |
packages/core/*.d.ts | Type definitions |
docs/SPEC.md | API documentation |
.claude/CLAUDE.md | If docs/ changed |
digraph change_flow {
"Non-trivial change?" [shape=diamond];
"Needs RFC?" [shape=diamond];
"Create RFC" -> "Discuss with user" -> "Update SPEC Decision Log";
"Make synchronized updates" -> "Verify tsc passes" -> "Done";
"Non-trivial change?" -> "Needs RFC?" [label="yes"];
"Needs RFC?" -> "Create RFC" [label="yes"];
"Needs RFC?" -> "Make synchronized updates" [label="no"];
"Update SPEC Decision Log" -> "Make synchronized updates";
}
When decision is made, add to SPEC.md:
### YYYY-MM-DD: [Decision Title]
**Context:** [What prompted this]
**Decision:** [What was decided]
**Rationale:** [Why]
**Alternatives rejected:** [What else was considered]