菜单
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.
用 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 making non-trivial changes, modifying public APIs, or proposing new framework features. Use when changes affect multiple files or require design decisions.
Use after any change to skeleton/, packages/core/, or docs/. Use to verify types compile and documentation is synchronized.
| name | kubit-researching-prior-art |
| description | 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. |
When designing subsystems, research how established frameworks solve the same problem. Capture findings in docs/BRAINDUMP.md or the relevant RFC.
| Framework | Strong Areas |
|---|---|
| Laravel | Eloquent ORM, Queue, Mail, Auth, Blade |
| AdonisJS | TypeScript patterns, decorators, Lucid ORM |
| Rails | ActiveRecord, conventions, generators |
| Inertia.js | SPA protocol, React SSR, forms |
| Remix/Next | React SSR, data loading, routing |
When studying a pattern:
| Scope | Where to capture |
|---|---|
| General philosophy | docs/BRAINDUMP.md |
| Specific subsystem research | Relevant RFC |
| Design decision | SPEC.md Decision Log |
## [Subsystem] Prior Art
### Laravel
- API: `Mail::to($user)->send(new OrderShipped($order))`
- Conventions: Mailables as classes, queued by default
- Extension: Custom transports via driver config
### AdonisJS
- API: Similar but TypeScript-native
- Conventions: Decorators for metadata
### Key Insights
- [What to adopt]
- [What to avoid]
- [Kubit-specific adaptation needed]
Class-based entities: Controllers, Models, Jobs, Mailables are classes Decorators/Annotations: Metadata on properties and methods Convention over configuration: Sensible defaults, override when needed Fluent APIs: Method chaining for configuration DI containers: Automatic dependency resolution