القائمة
This skill provides guidance for creating feature specifications in the Spec-Driven Development process.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
This skill provides guidance for implementing secure authentication using Better Auth for Next.js frontend and JWT verification for FastAPI backend.
This skill helps create React chat widgets using the ChatKit React library, following best practices for floating chat interfaces with thread persistence and proper configuration.
This skill helps create ChatKit server implementations that integrate with databases and openai-agents, following best practices for conversation management and message persistence.
This skill provides functionality to properly expose a ChatKit server via FastAPI routes. It handles the integration between FastAPI request/response cycle and the ChatKit server, with proper request processing and response handling.
This skill helps create ChatKit store implementations with database integration, following best practices and avoiding common errors we've solved in previous implementations.
Comprehensive DAPR (Distributed Application Runtime) skill for building distributed microservices from hello world to professional production systems. Provides guidance on DAPR setup, building blocks (service invocation, state management, pub/sub, actors, secrets), sidecar configuration, component configuration, and Kubernetes integration for scalable distributed applications.
| name | specification-writing-skill |
| description | This skill provides guidance for creating feature specifications in the Spec-Driven Development process. |
This skill provides guidance for creating feature specifications in the Spec-Driven Development process.
The project is organized into 5 distinct phases:
specs/
├── phase-01/
│ ├── 001-<feature-name>/
│ │ └── spec.md
│ └── 002-<feature-name>/
│ └── spec.md
├── phase-02/
│ └── 001-<feature-name>/
│ └── spec.md
├── phase-03/
│ └── 001-<feature-name>/
│ └── spec.md
├── phase-04/
│ └── 001-<feature-name>/
│ └── spec.md
└── phase-05/
└── 001-<feature-name>/
└── spec.md
Each feature specification includes:
Prompt History Records are stored in:
history/prompts/
├── phase-01/
│ ├── 001-todo-app/
│ │ └── <ID>-<slug>.<stage>.prompt.md
│ └── 002-<feature-name>/
│ └── <ID>-<slug>.<stage>.prompt.md
├── phase-02/
│ ├── 001-<feature-name>/
│ │ └── <ID>-<slug>.<stage>.prompt.md
│ └── 002-<feature-name>/
│ └── <ID>-<slug>.<stage>.prompt.md
└── general/
└── <ID>-<slug>.general.prompt.md
{###}-{feature-name} (e.g., 001-todo-app)phase-{nn}/{###}-{feature-name} (e.g., phase-01/001-todo-app){ID}-{slug}.{stage}.prompt.md (e.g., 1-todo-app-created.spec.prompt.md)