[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BXD5TSFST87ME4YXRNTVX5":3,"skill-same:01M6BXD5TSFST87ME4YXRNTVX5":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":29,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6BXD5TSFST87ME4YXRNTVX5","deployer-workflow",null,"Full-stack development workflow that orchestrates deployer agents (backend, frontend, database, testing, review) in a phased pipeline. Asks which backend language (Java\u002FGo\u002FRust) then runs all agents.","diegopacheco\u002Fai-playground","diegopacheco","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121278?v=4","01M6BXCP8P7GGSJ8M1W2MFDTGT","Diego Pacheco","01M6BXCPD3WM51H465XW9YM4BV",21,"Unlicense","https:\u002F\u002Fgithub.com\u002Fdiegopacheco\u002Fai-playground\u002Fblob\u002Fmain\u002Fpocs\u002Fadwf-twitter-like-opus-4-6-v3-skill\u002F.claude\u002Fskills\u002Fworkflow-skill\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[30,31,32,33,34,35,36,37,38,39,40,41,42],"workflow","deployer workflow","testing","frontend","review","go","rust","development","database","java","pipeline","Bash","stack","2026-11-10 10:12:30",false,"---\nname: deployer-workflow\ndescription: Full-stack development workflow that orchestrates deployer agents (backend, frontend, database, testing, review) in a phased pipeline. Asks which backend language (Java\u002FGo\u002FRust) then runs all agents.\nallowed-tools: [Read, Write, Edit, Bash, Glob, Grep, Task, AskUserQuestion, TaskCreate, TaskUpdate, TaskList]\n---\n\n# Deployer Workflow Skill\n\n## Global Context\n- User request: $ARGUMENTS\n- Agents directory: `agents\u002F`\n- Agent definition files: all markdown files in `agents\u002F`\n- Design doc: `design-doc.md` (project root)\n- Progress file: `todo.md` (project root)\n- Mistakes file: `mistakes.md` (project root)\n- Review folder: `review\u002F{yyyy-MM-dd}\u002F`\n- Changelog: `changelog.md` (project root)\n- README: `README.md` (project root)\n\n## Agents\n\nThere are 5 agents total:\n1. **Backend Developer** (java-backend-developer-agent.md \u002F go-backend-developer-agent.md \u002F rust-backend-developer-agent.md)\n2. **React Developer** (react-developer-agent.md)\n3. **Relational DBA** (relational-dba-agent.md)\n4. **Testing Agent** (testing-agent.md) - handles unit tests, integration tests, UI tests (Playwright), stress tests (K6)\n5. **Reviewer Agent** (reviewer-agent.md) - handles code review, security review, design doc sync, feature docs, changes summary\n\n## Rules\n- If $ARGUMENTS is empty, ask: \"What do you want to build? Describe the feature or application.\"\n- Ask backend language using AskUserQuestion with options:\n  - Java: Spring Boot 4.x, Java 25\n  - Go: Go 1.25+, Gin Gonic\n  - Rust: Rust 1.93+, Axum\u002FActix-web\n- Read all agent definitions from `agents\u002F` and pass them as context to subagents.\n- Use Task subagents with `subagent_type: \"general-purpose\"`.\n- Include user request, relevant files, and the full agent definition in each subagent prompt.\n- Phase order: Build -> Test -> Review -> Changelog -> README.\n- Phase dependencies: Test depends on Build. Review depends on Build + Test. Changelog depends on all previous phases.\n- After each phase, update `todo.md` by marking completed items with `[x]`.\n\n## Mistakes Tracking\n\n- `mistakes.md` in the project root tracks all build failures, test failures, and issues across all phases.\n- Every agent MUST read `mistakes.md` before starting work to avoid repeating past mistakes.\n- Every agent MUST append new mistakes\u002Fissues they encounter to `mistakes.md` with the phase name and a short description.\n- At the start of the workflow, create `mistakes.md` if it does not exist with a header `# Mistakes Log`.\n- Format: `- [Phase N: Name] description of the mistake or issue and how it was fixed`\n\n## Build and Test Enforcement\n\n- The build MUST compile and pass before moving to Phase 2 (Test).\n- ALL tests (unit, integration, UI, stress) MUST pass before moving to Phase 3 (Review).\n- If the build fails, fix it immediately. Do not proceed until the build is green.\n- If any test fails, debug and fix the root cause. Re-run all tests until they all pass.\n- After fixing build or test failures, record what went wrong and how it was fixed in `mistakes.md`.\n- At the end of Phase 1, run the full build and verify it succeeds.\n- At the end of Phase 2, run all tests and verify they all pass.\n\n## Step 1: Review Plan\nUse AskUserQuestion with checkboxes (all checked by default) and allow unchecking. Store selections and skip unchecked items:\n- Phase 1: Build\n  - Build Components (Backend, Frontend, Database)\n  - Verify Build (compile, run, connectivity)\n- Phase 2: Test\n  - All Tests (Unit, Integration, UI Playwright, K6 Stress)\n- Phase 3: Review\n  - Full Review (Code, Security, Design Doc Sync, Feature Docs, Changes Summary)\n- Changelog & README Update\n\nInitialize `todo.md` with current date (yyyy-MM-dd) and all selected items as `[ ]`.\n\n## Step 2: Design Doc\nCreate `design-doc.md` with:\n- Architecture overview\n- Backend API endpoints and responsibilities\n- Frontend components and interactions\n- Database schema design\n- Integration points between frontend, backend, database\n\n## Phase 1: Build\n### Build Components (parallel)\nSpawn 3 subagents in parallel:\n1. **Backend Developer**: use chosen language agent (java\u002Fgo\u002Frust backend agent). Implement backend per `design-doc.md`. Agent MUST read `mistakes.md` first.\n2. **React Developer**: use react-developer-agent.md. Implement frontend per `design-doc.md`. Agent MUST read `mistakes.md` first.\n3. **Relational DBA**: use relational-dba-agent.md. Design and create DB schema per `design-doc.md`. Agent MUST read `mistakes.md` first.\n\n### Verify Build\nAfter all 3 subagents complete:\n- Verify DB schema\u002Fmigrations apply successfully.\n- Verify backend compiles, builds, and runs with DB connection.\n- Verify frontend builds and can be served and connects to backend.\n- If ANY build step fails: fix the issue, record it in `mistakes.md`, and re-verify.\n- Do NOT proceed to Phase 2 until the full build is green.\n\n## Phase 2: Test\nSpawn 1 subagent:\n1. **Testing Agent**: use testing-agent.md. Run all tests (unit, integration, UI Playwright, K6 stress) for all code from Phase 1. Agent MUST read `mistakes.md` first.\n\nAfter the testing agent completes:\n- Verify ALL tests pass by running the full test suite.\n- If ANY test fails: fix the issue, record it in `mistakes.md`, re-run all tests.\n- Do NOT proceed to Phase 3 until all tests are green.\n\n## Phase 3: Review\nCreate `review\u002F{current-date}\u002F`.\nSpawn 1 subagent:\n1. **Reviewer Agent**: use reviewer-agent.md. Perform code review, security review, sync design doc, write feature docs, and summarize changes. Agent MUST read `mistakes.md` first. Outputs:\n   - `review\u002F{current-date}\u002Fcode-review.md`\n   - `review\u002F{current-date}\u002Fsec-review.md`\n   - `review\u002F{current-date}\u002Ffeatures.md`\n   - `review\u002F{current-date}\u002Fsummary.md`\n   - Updates `design-doc.md`\n\nIf critical issues are found, fix them and record in `mistakes.md`.\n\n## Changelog\nCreate `changelog.md` using git info:\n- Use `git status`, `git diff`, `git log`.\n- Include current date, what was built, files created\u002Fmodified, test coverage summary, review findings and fixes, docs generated, remaining issues or recommendations.\n\n## README\nUpdate\u002Fcreate `README.md` with:\n- Overview\n- Links to: `design-doc.md`, `review\u002F{current-date}\u002Fcode-review.md`, `review\u002F{current-date}\u002Fsec-review.md`, `review\u002F{current-date}\u002Ffeatures.md`, `review\u002F{current-date}\u002Fsummary.md`, `changelog.md`\n- Summary highlights from `review\u002F{current-date}\u002Fsummary.md`\n- Quick start (backend, frontend, database)\n","# Deployer Workflow Skill\n\n## Global Context\n- User request: $ARGUMENTS\n- Agents directory: `agents\u002F`\n- Agent definition files: all markdown files in `agents\u002F`\n- Design doc: `design-doc.md` (project root)\n- Progress file: `todo.md` (project root)\n- Mistakes file: `mistakes.md` (project root)\n- Review folder: `review\u002F{yyyy-MM-dd}\u002F`\n- Changelog: `changelog.md` (project root)\n- README: `README.md` (project root)\n\n## Agents\n\nThere are 5 agents total:\n1. **Backend Developer** (java-backend-developer-agent.md \u002F go-backend-developer-agent.md \u002F rust-backend-developer-agent.md)\n2. **React Developer** (react-developer-agent.md)\n3. **Relational DBA** (relational-dba-agent.md)\n4. **Testing Agent** (testing-agent.md) - handles unit tests, integration tests, UI tests (Playwright), stress tests (K6)\n5. **Reviewer Agent** (reviewer-agent.md) - handles code review, security review, design doc sync, feature docs, changes summary\n\n## Rules\n- If $ARGUMENTS is empty, ask: \"What do you want to build? Describe the feature or application.\"\n- Ask backend language using AskUserQuestion with options:\n  - Java: Spring Boot 4.x, Java 25\n  - Go: Go 1.25+, Gin Gonic\n  - Rust: Rust 1.93+, Axum\u002FActix-web\n- Read all agent definitions from `agents\u002F` and pass them as context to subagents.\n- Use Task subagents with `subagent_type: \"general-purpose\"`.\n- Include user request, relevant files, and the full agent definition in each subagent prompt.\n- Phase order: Build -> Test -> Review -> Changelog -> README.\n- Phase dependencies: Test depends on Build. Review depends on Build + Test. Changelog depends on all previous phases.\n- After each phase, update `todo.md` by marking completed items with `[x]`.\n\n## Mistakes Tracking\n\n- `mistakes.md` in the project root tracks all build failures, test failures, and issues across all phases.\n- Every agent MUST read `mistakes.md` before starting work to avoid repeating past mistakes.\n- Every agent MUST append new mistakes\u002Fissues they encounter to `mistakes.md` with the phase name and a short description.\n- At the start of the workflow, create `mistakes.md` if it does not exist with a header `# Mistakes Log`.\n- Format: `- [Phase N: Name] description of the mistake or issue and how it was fixed`\n\n## Build and Test Enforcement\n\n- The build MUST compile and pass before moving to Phase 2 (Test).\n- ALL tests (unit, integration, UI, stress) MUST pass before moving to Phase 3 (Review).\n- If the build fails, fix it immediately. Do not proceed until the build is green.\n- If any test fails, debug and fix the root cause. Re-run all tests until they all pass.\n- After fixing build or test failures, record what went wrong and how it was fixed in `mistakes.md`.\n- At the end of Phase 1, run the full build and verify it succeeds.\n- At the end of Phase 2, run all tests and verify they all pass.\n\n## Step 1: Review Plan\nUse AskUserQuestion with checkboxes (all checked by default) and allow unchecking. Store selections and skip unchecked items:\n- Phase 1: Build\n  - Build Components (Backend, Frontend, Database)\n  - Verify Build (compile, run, connectivity)\n- Phase 2: Test\n  - All Tests (Unit, Integration, UI Playwright, K6 Stress)\n- Phase 3: Review\n  - Full Review (Code, Security, Design Doc Sync, Feature Docs, Changes Summary)\n- Changelog & README Update\n\nInitialize `todo.md` with current date (yyyy-MM-dd) and all selected items as `[ ]`.\n\n## Step 2: Design Doc\nCreate `design-doc.md` with:\n- Architecture overview\n- Backend API endpoints and responsibilities\n- Frontend components and interactions\n- Database schema design\n- Integration points between frontend, backend, database\n\n## Phase 1: Build\n### Build Components (parallel)\nSpawn 3 subagents in parallel:\n1. **Backend Developer**: use chosen language agent (java\u002Fgo\u002Frust backend agent). Implement backend per `design-doc.md`. Agent MUST read `mistakes.md` first.\n2. **React Developer**: use react-developer-agent.md. Implement frontend per `design-doc.md`. Agent MUST read `mistakes.md` first.\n3. **Relational DBA**: use relational-dba-agent.md. Design and create DB schema per `design-doc.md`. Agent MUST read `mistakes.md` first.\n\n### Verify Build\nAfter all 3 subagents complete:\n- Verify DB schema\u002Fmigrations apply successfully.\n- Verify backend compiles, builds, and runs with DB connection.\n- Verify frontend builds and can be served and connects to backend.\n- If ANY build step fails: fix the issue, record it in `mistakes.md`, and re-verify.\n- Do NOT proceed to Phase 2 until the full build is green.\n\n## Phase 2: Test\nSpawn 1 subagent:\n1. **Testing Agent**: use testing-agent.md. Run all tests (unit, integration, UI Playwright, K6 stress) for all code from Phase 1. Agent MUST read `mistakes.md` first.\n\nAfter the testing agent completes:\n- Verify ALL tests pass by running the full test suite.\n- If ANY test fails: fix the issue, record it in `mistakes.md`, re-run all tests.\n- Do NOT proceed to Phase 3 until all tests are green.\n\n## Phase 3: Review\nCreate `review\u002F{current-date}\u002F`.\nSpawn 1 subagent:\n1. **Reviewer Agent**: use reviewer-agent.md. Perform code review, security review, sync design doc, write feature docs, and summarize changes. Agent MUST read `mistakes.md` first. Outputs:\n   - `review\u002F{current-date}\u002Fcode-review.md`\n   - `review\u002F{current-date}\u002Fsec-review.md`\n   - `review\u002F{current-date}\u002Ffeatures.md`\n   - `review\u002F{current-date}\u002Fsummary.md`\n   - Updates `design-doc.md`\n\nIf critical issues are found, fix them and record in `mistakes.md`.\n\n## Changelog\nCreate `changelog.md` using git info:\n- Use `git status`, `git diff`, `git log`.\n- Include current date, what was built, files created\u002Fmodified, test coverage summary, review findings and fixes, docs generated, remaining issues or recommendations.\n\n## README\nUpdate\u002Fcreate `README.md` with:\n- Overview\n- Links to: `design-doc.md`, `review\u002F{current-date}\u002Fcode-review.md`, `review\u002F{current-date}\u002Fsec-review.md`, `review\u002F{current-date}\u002Ffeatures.md`, `review\u002F{current-date}\u002Fsummary.md`, `changelog.md`\n- Summary highlights from `review\u002F{current-date}\u002Fsummary.md`\n- Quick start (backend, frontend, database)\n",{"name":5,"description":7,"allowed-tools":48},[49,50,51,41,52,53,54,55,56,57,58],"Read","Write","Edit","Glob","Grep","Task","AskUserQuestion","TaskCreate","TaskUpdate","TaskList","main","90d379e95fcc23dd9759654c345424e1752b0f3a","pocs\u002Fadwf-twitter-like-opus-4-6-v3-skill\u002F.claude\u002Fskills\u002Fworkflow-skill",9,"https:\u002F\u002Fgithub.com\u002Fdiegopacheco\u002Fai-playground","https:\u002F\u002Fgithub.com\u002Fdiegopacheco","http:\u002F\u002Fdiego-pacheco.blogspot.com","Brazilian Hands-on Software Architect | 20+ years in Tech | Author | Father. Opinions are my own!","2026-11-07 09:01:46",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add diegopacheco\u002Fai-playground --skill deployer-workflow",{"tool":74,"command":75},"bunx","bunx skills add diegopacheco\u002Fai-playground --skill deployer-workflow",{"tool":77,"command":78},"pnpm","pnpm dlx skills add diegopacheco\u002Fai-playground --skill deployer-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdiegopacheco\u002Fai-playground\u002Fblob\u002Fmain\u002Fpocs\u002Fadwf-twitter-like-opus-4-6-v3-skill\u002F.claude\u002Fskills\u002Fworkflow-skill\u002FSKILL.md",true,[],[83,99,109,122,138,156],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":92,"publishedAt":43},"01M6WJ537DN520XY8MSW9ZV0RP","word-count","Counts the words, lines and characters of a text or a file.","https:\u002F\u002Fgithub.com\u002Fdiegopacheco\u002Fai-playground\u002Fblob\u002Fmain\u002Fpocs\u002Fskills-gateway-router\u002Fupstream-skills\u002Ftext-skills\u002Fword-count\u002FSKILL.md",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",[93,94,95,96,97,98],"count","word count","Word","characters","text","file",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":43},"01M6WJ4Y2GT5SECWAKKYHGES4F","slugify","Turns a title or a sentence into a URL slug, lowercase words joined by hyphens with accents removed.","https:\u002F\u002Fgithub.com\u002Fdiegopacheco\u002Fai-playground\u002Fblob\u002Fmain\u002Fpocs\u002Fskills-gateway-router\u002Fupstream-skills\u002Ftext-skills\u002Fslugify\u002FSKILL.md",[],[101,106,107,108],"title","with","URL",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":43},"01M6WJ4V9CWHT9NVCD441VK5MH","json-format","Validates a JSON file and pretty prints it with two space indentation, or reports where the JSON is invalid.","https:\u002F\u002Fgithub.com\u002Fdiegopacheco\u002Fai-playground\u002Fblob\u002Fmain\u002Fpocs\u002Fskills-gateway-router\u002Fupstream-skills\u002Fdev-skills\u002Fjson-format\u002FSKILL.md",[],[116,117,118,98,119,120,121,107],"json","format","json format","reports","invalid","it",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":43},"01M6WJ4QMRKW8EFP71F4KS2DHE","commit-message","Writes a conventional commit message for the staged git changes.","https:\u002F\u002Fgithub.com\u002Fdiegopacheco\u002Fai-playground\u002Fblob\u002Fmain\u002Fpocs\u002Fskills-gateway-router\u002Fupstream-skills\u002Fdev-skills\u002Fcommit-message\u002FSKILL.md",[],[129,130,131,132,133,134,135,136,137],"commit","commit message","message","git","conventional commit","for","changes","staged","conventional commit message",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":43},"01M6WJ4MAM2CJH0GWYXFBB9GQC","skills-gateway","Gateway and router to a catalog of skills that are not registered directly. Use it before any task a specialized skill could handle, such as text, JSON or git chores. It finds the right skill and loads its instructions.","https:\u002F\u002Fgithub.com\u002Fdiegopacheco\u002Fai-playground\u002Fblob\u002Fmain\u002Fpocs\u002Fskills-gateway-router\u002F.claude\u002Fskills\u002Fskills-gateway\u002FSKILL.md",[],[145,146,121,147,148,132,41,116,97,149,150,151,152,153,154,155],"skills gateway","gateway","task","loads","node","specialized","instructions","catalog","use","router","as",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":43},"01M6M2PYJJQKMWGX7XT7ZJK0H3","decision-log","Record, list, show and supersede architecture decisions that persist across sessions in the shared agent infra state store. Use when the user says \"record this decision\", \"log an ADR\", \"what did we decide about\", \"list decisions\", or \"supersede decision\".","https:\u002F\u002Fgithub.com\u002Fdiegopacheco\u002Fai-playground\u002Fblob\u002Fmain\u002Fpocs\u002Fagent-skills-infra-poc\u002Fskills\u002Fdecision-log\u002FSKILL.md",[],[163,164,165,166,167,168,169,170,171,172,153,173,174,175,176,177,178,179,180,181],"decision log","log","decision","persist","architecture","state","adr","decide","decisions","list","show","infra","record","across","shared","store","about","supersede","sessions"]