fagemx/dogfood
.claude/skills/dogfood/SKILL.md
Test Prismstack by running a real domain through the full flow (plan → build → check). Records issues found for fixing. The ultimate integration test. Trigger: "dogfood", "test with real domain", "integration test", "try it for real" Do NOT use when: just want to run install tests (use `bash test/install-test.sh`)
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add fagemx/prismstack dogfoodInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 12:58 PM5.2s1 file scanned
SKILL.md
- name:
- dogfood
- description:
- |
- Trigger:
- dogfood", "test with real domain", "integration test", "try it for real
- Do NOT use when:
- just want to run install tests (use `bash test/install-test.sh`)
- user_invocable:
- true
<!-- Internal maintenance skill — edit this file directly -->
/dogfood: Integration Test With a Real Domain
You are a QA tester dogfooding Prismstack. You run a real domain through the full product flow and record every issue you find.
Phase 0: Pick a Test Domain
Parse $ARGUMENTS for a domain name. If not provided, suggest:
- 小型咖啡店行銷 (small coffee shop marketing) — simple, ~10 skills, fast
- 獨立遊戲開發工作流 (indie game dev workflow) — medium complexity
- 自由接案者專案管理 (freelancer project management) — diverse skill types
Ask the user to pick one or provide their own domain.
Create a temp working directory:
_DOGFOOD_DIR=$(mktemp -d)/dogfood-test
mkdir -p "$_DOGFOOD_DIR"
echo "Working in: $_DOGFOOD_DIR"
Phase 1: Run /domain-plan
Read skills/domain-plan/SKILL.md and follow its flow for the test domain.
Execute the planning phase as if you were a real user. Record:
- Did it work? Did the skill produce a complete domain plan?
- Awkward moments: Any point where the flow was confusing or required backtracking?
- Errors: Any crashes, missing files, or broken references?
- Timing: Roughly how many tool calls / how long did the phase take?
- Output quality: Is the generated plan actually useful for the domain?
Save the plan output to $_DOGFOOD_DIR/domain-plan-output/.
Phase 2: Run /domain-build
Read skills/domain-build/SKILL.md and follow its flow using the plan from Phase 1.
Build the domain stack in $_DOGFOOD_DIR/generated-stack/.
Record the same categories as Phase 1, plus:
- Skill count: Did it generate the expected number of skills?
- Skill structure: Do generated skills follow skill-craft-guide structure?
- Shared resources: Were methodology files and shared context created?
- Completeness: Can each generated skill actually be invoked?
Phase 3: Run /skill-check on the Generated Stack
Read skills/skill-check/SKILL.md and run it with --all on the generated domain stack.
Record:
- Scores: What did each generated skill score?
- Common issues: What patterns appear across multiple skills?
- Fix loop: Did the fix loop workflow work? Could issues be resolved?
- Rubric coverage: Were all 15 dimensions actually scored?
Phase 4: Issue Report
Compile all recorded issues into a structured report:
# Dogfood Report: [domain name]
Date: YYYY-MM-DD
Prismstack version: <from VERSION>
## Summary
- Domain: [name]
- Skills generated: N
- Average quality score: X.XX / 5.00
- Issues found: N (C critical, I important, M minor)
## Issues
### Issue 1: [title]
- **Phase**: plan / build / check
- **Severity**: critical / important / minor
- **What happened**: description
- **Expected**: what should have happened
- **Root cause**: which Prismstack skill or methodology caused it
- **Suggested fix**: use /skill-dev on X, or edit methodology Y
### Issue 2: ...
Save the report to .claude/skills/dogfood/last-dogfood-report.md.
Cleanup
Ask the user:
- Keep the generated stack in
$_DOGFOOD_DIRfor manual inspection? - Delete it to save space?
Act on their choice.
Output
Present:
- Pass/Fail: Did the full flow complete without critical errors?
- Score Summary: Average quality of generated skills
- Top Issues: The 3 most impactful issues found
- Next Steps: Which maintenance skill to run for each fix (/skill-dev, /self-check, /methodology-sync)
Related Skills
fagemx/workflow-edit
data-ai
VerifiedTrustedCommunity
查看和編輯 domain stack 的 artifact flow、skill 串接、workflow graph。 Trigger: 用戶說「改 workflow」、「skill 串接」、「調整流程」、「看 artifact flow」。 Do NOT use when: 要改 skill 內部（用 /skill-edit）。 Do NOT use when: 要加新 skill（用 /skill-gen）。 上游：現有 domain stack。 下游：被修改的 skill 們。 產出：更新後的 workflow-graph.md + 修改的 SKILL.md 檔案。
SKILL.mdUpdated Apr 17, 2026
fagemx/tool-builder
tools
VerifiedTrustedCommunity
打造工具型 skill。雙層架構： Layer 1（直接做）：幫用戶自動化一個具體目標。 Layer 2（產出 skill）：產出可重複使用的工具型 skill。 涵蓋：browser automation、API 串接、CLI 工具、檔案處理、外部服務。 Trigger: 用戶說「自動化這個網站」、「做一個工具」、「API 串接」、「幫我寫腳本」。 Do NOT use when: 要建 domain skill（用 /skill-gen）。 Do NOT use when: 要轉換已有材料為 skill（用 /source-convert）。 上游：用戶需求 + 目標平台。 下游：/skill-check review。 產出：Layer 1 = working automation / Layer 2 = SKILL.md + scripts/。
SKILL.mdUpdated Apr 17, 2026
fagemx/super-guide
devops
VerifiedTrustedCommunity
Prismstack 超級引導員 — 實戰教練。 Trigger: 用戶不知道下一步、想學串 pipeline、卡關倦怠、想理解 skill 原理、 問「怎麼用」「為什麼這樣設計」「怎麼自動化」。 Do NOT use when: 用戶明確知道要跑哪個 skill（用 /prism-routing）。 Do NOT use when: 用戶要規劃新 domain stack（用 /domain-plan）。 並存：/prism-routing 是快速路由（熟手用），/super-guide 是教學引導（需要理解的人用）。 上游：任何 skill 的產出、用戶的 domain stack。 下游：任何 Prismstack skill（引導完畢後可直接啟動）。
SKILL.mdUpdated Apr 17, 2026
fagemx/source-convert
tools
VerifiedTrustedCommunity
把任何外部來源轉換成 gstack skill 或 skill 片段。 來源類型：skill repo、prompt、影片、文章、書、SOP、代碼庫、ECC skill、git history、用戶想法。 Trigger: 用戶說「這篇文章很好」、「這個 repo 想用」、「把這個變成 skill」、「轉換」。 Do NOT use when: 要從零建 skill（用 /skill-gen）。 Do NOT use when: 要建工具型 skill（用 /tool-builder）。 上游：任何外部來源。 下游：/skill-edit 或 /skill-gen（取決於 placement）。 產出：轉換後的 skill content（新 skill / section / patch）。
SKILL.mdUpdated Apr 17, 2026