메뉴
Generate, update, or review Dalgo user-facing documentation. Use when the user asks to document a feature, write a docs page, update existing docs, or after a PR ships to refresh affected docs.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Draft a new Dalgo release notes entry on dalgo_docs from the latest release tags of DDP_backend and webapp_v2. Use when the user asks to write, publish, or update release notes after a release ships.
Use when implementing a feature plan end-to-end across the Dalgo backend (DDP_backend, Django) and frontend (webapp_v2, Next.js). Triggers on "execute this plan", "implement this feature", "build this from the plan", working from a plan.md / tasks.md.
Use when the user wants to create a Linear issue from a feature plan document (plan.md) generated by /engineering/plan-feature or /engineering/ship-feature. Triggers on: "create linear issue from plan", "post this to linear", "make an issue for this plan", "communicate this plan on linear".
Transform messy ideas into structured PRDs that get stakeholder alignment before engineering starts building. Use when: write prd, product requirements, requirements document, feature spec.
Writing rules for plans, specs, research notes, and any user-facing explanation in Dalgo. Use whenever producing a plan.md, research.md, spec.md, or explaining a feature/decision to the user — so the reader (a non-technical NGO program manager, a first-time engineer on the codebase, or a busy reviewer skimming on a phone) can follow without backfilling jargon. Triggered by the planning, spec-writing, and design-handoff commands; also invoke directly when the user says "explain in simple language", "give me an example", or asks you to rewrite something more plainly.
Apply Tal Raviv's technology philosophy when evaluating tools, building features, making product or architecture decisions, or explaining technical concepts. Use when the user asks to demystify, evaluate, prototype, or think critically about any technology decision.
| name | documentation |
| description | Generate, update, or review Dalgo user-facing documentation. Use when the user asks to document a feature, write a docs page, update existing docs, or after a PR ships to refresh affected docs. |
Reference and workflow for generating Dalgo's user-facing Docusaurus documentation. Lives in the dalgo_docs/ repo (symlinked into dalgo-core/).
Trigger when the user asks to:
Start by reading workflow.md.
The sidebar mirrors the product left-nav exactly. Sections 1–3 are docs-only orientation. Sections 4–9 match the product navigation order. Section 10 is support convention.
Rule: If a section exists in the product nav, it exists in the docs sidebar at the same level and with the same label. Don't invent groupings that don't exist in the product.
quickstart/) — short linear path for first-time users. Each page is one screen. Ends with "→ Next" links. Links into reference pages rather than duplicating them.:::note For implementation partners callouts on pages like Warehouse setup, Transform repo switching, and User Management.| File | Purpose |
|---|---|
workflow.md | Step-by-step process from research to published markdown |
sidebar.md | Sidebar structure + patterns for adding new entries |
repo-structure.md | Doc repo layout + screenshot policy |
style-writing.md | Audience + voice + instructions format + anti-patterns |
style-page.md | Page structure + quickstart template |
style-admonitions.md | Admonition rules + conditional features |
style-images.md | Image naming + directory mapping + markdown syntax |