メニュー
Update the DevFlow agent system to the latest version from the source repo (github.com/ljojua1998/skills) and reinstall it here. Use when the user asks to update/upgrade DevFlow or sync the agent system.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | devflow-update |
| description | Update the DevFlow agent system to the latest version from the source repo (github.com/ljojua1998/skills) and reinstall it here. Use when the user asks to update/upgrade DevFlow or sync the agent system. |
${CLAUDE_SKILL_DIR})
is under the user's home .claude folder → scope is global; otherwise →
project (target = this project's root).~/.devflow-src:
git -C ~/.devflow-src pull --ff-onlygit clone --depth 1 https://github.com/ljojua1998/skills.git ~/.devflow-src
Note the old→new commit range.powershell -ExecutionPolicy Bypass -File ~/.devflow-src/install.ps1 -Force
plus -Global (global scope) or -Target "<project root>" (project scope).~/.devflow-src/install.sh --force plus --global or the project path.git -C ~/.devflow-src log --oneline <old>..<new> as the changelog,
list of updated files from the installer output, and remind the user to restart
the Claude Code session so updated agents/skills load.If the local source repo (the DevFlow development folder) is this very project
(it contains install.ps1 and .claude/agents/planner.md in git), don't
self-update — tell the user this is the source repo itself.
Database engineering standards for PostgreSQL, MySQL, MongoDB, Supabase and Firebase/Firestore — schema/index design, security, and the per-engine gotchas an agent gets wrong. Loaded on top of backend-craft when a ticket touches the database. Use when designing schema, queries, migrations or data-access.
Next.js App Router full-stack standards — server/client boundaries, the four caching layers, server-action security, route handlers, rendering/streaming, metadata, middleware limits, and Next-specific testing. Loaded on top of react-craft (and alongside backend-craft for server code) when the ticket's stack is Next.js. Use when building any Next.js route, action, or API surface.
Headless QA tooling for driving real test tools from the CLI — Postman/Newman (functional + contract), OWASP ZAP + nuclei (security/DAST, the agent-drivable substitute for Burp), and k6/JMeter/autocannon (load). Use when running a comprehensive QA/security/load sweep against a running app.
Full delivery pipeline — takes a feature/project request, plans it into Jira-like markdown tickets, builds each ticket with specialized developer agents, then runs QA, security and code-audit agents, loops a debugger agent over findings until clean, and closes with a final report. Use when the user asks to build a feature or project end-to-end, or invokes /ship.
Express.js (Node) engineering standards — layering, async error handling (Express 4 vs 5), boundary validation, security middleware, graceful shutdown, and testing. Loaded on top of backend-craft when the ticket's stack is Express. Use when building Express APIs.
NestJS engineering standards — feature-module architecture, DI discipline, DTO validation, the guard/interceptor/pipe/filter split, config, TypeORM/Prisma, and testing. Loaded on top of backend-craft when the ticket's stack is NestJS. Use when building NestJS APIs.