菜单
Guided tour of changes or codebase - explains how things work conceptually rather than listing changes mechanically. Use anytime you're asked to explain, review, walk through, or summarize work, branch changes, or codebase architecture.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
DDD planning and review workflow for greenfield systems and brownfield codebases. Use when shaping bounded contexts, ubiquitous language, aggregates, invariants, integration boundaries, or reviewing an existing model for DDD fit.
Copy the skills collection from /Users/shrivatsa/Documents/dev-setup/skills into the current repository, another repository, or an explicit skills directory. Use when the user asks to copy, sync, install, update, or bring over their dev-setup skills.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
Expert HIPAA compliance assistant for healthcare and software contexts. Use this skill whenever the user mentions HIPAA, PHI (Protected Health Information), ePHI, covered entities, business associates, healthcare data privacy, medical records, health information security, BAA (Business Associate Agreements), or any compliance review involving patient data. Also trigger for requests to draft privacy notices, HIPAA policies, consent forms, security risk assessments, or breach notification letters. Use for developers building healthcare software who need technical safeguard guidance (encryption, access controls, audit logs), compliance officers reviewing documents or procedures, and anyone asking "is this HIPAA compliant?" or "what does HIPAA require for X?". When in doubt about whether a healthcare or data privacy question falls under this skill — use it.
Outcome-first architecture discovery and recommendation skill. Use when you need to iteratively clarify requirements, ask leading questions about business goals and constraints, maintain a running intake file so users do not repeat themselves, and produce a sharp architecture recommendation with tradeoffs and risks.
Add, remove, or refine research fields for an existing research outline, with concise evidence-first output.
| name | explain |
| description | Guided tour of changes or codebase - explains how things work conceptually rather than listing changes mechanically. Use anytime you're asked to explain, review, walk through, or summarize work, branch changes, or codebase architecture. |
When the user asks you to explain changes, review what's on a branch, walk through the codebase, or understand how something works, use this approach.
Conceptual clarity over mechanical completeness. Lead with the mental model, then layer in specifics that illuminate it. This isn't about dumbing things down - the user may be a core maintainer who knows this code intimately. It's about explanations that build understanding rather than enumerate changes.
Talk to me like you're explaining this to your colleague who knows the project but wants to understand this particular work - what you did, how it fits together, why it's shaped this way. Conversational, not documentary. Express enthusiasm when something is elegant. Invite follow-up. Don't quote ADR language or doc-speak - say it how you'd actually say it.
If the user indicates they lack context on something specific, adjust accordingly. But default to assuming expertise.
These are useless for understanding.
Provide a guided tour that builds understanding.
Lead with the conceptual model: What is this system trying to do? What are the key abstractions? How do they relate to each other?
The formal behavior: How does the system work now? What are the invariants, the contracts, the mental model someone needs to have?
What's new or different: If explaining changes, what shifted conceptually? Not "added function X" but "we now support Y, which means Z."
What this enables: Developer-facing implications. What can someone do now that they couldn't before? What patterns does this unlock?
What we're teeing up: If this is setting up for future work, say so. Help the user see the trajectory.
