spectra-analyze
harrychuang/cursor-skills/.claude/skills/spectra-analyze/SKILL.md
Analyze artifact consistency for a change
One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
harrychuang/cursor-skills/.claude/skills/spectra-analyze/SKILL.md
Analyze artifact consistency for a change
harrychuang/cursor-skills/.claude/skills/spectra-apply/SKILL.md
Implement or resume tasks from a Spectra change
Often used withspectra-commit
harrychuang/cursor-skills/.claude/skills/spectra-archive/SKILL.md
Archive a completed change
Often used withspectra-commit
harrychuang/cursor-skills/.claude/skills/spectra-audit/SKILL.md
Audit changed code for security sharp edges — dangerous defaults, type confusion, and silent failures
Often used withspectra-commit
harrychuang/cursor-skills/.claude/skills/spectra-commit/SKILL.md
Commit files related to a specific Spectra change
harrychuang/cursor-skills/.claude/skills/spectra-debug/SKILL.md
Systematically debug a problem using a four-phase workflow
Often used withspectra-commit
harrychuang/cursor-skills/.claude/skills/spectra-discuss/SKILL.md
Have a focused discussion about a topic and reach a conclusion
Often used withspectra-commit
harrychuang/cursor-skills/.claude/skills/spectra-drift/SKILL.md
Detect drift between a Spectra change and the current codebase state
harrychuang/cursor-skills/.claude/skills/spectra-ingest/SKILL.md
Update an existing Spectra change from external context
Often used withspectra-commit
harrychuang/cursor-skills/.claude/skills/spectra-propose/SKILL.md
Create a change proposal with all required artifacts
Often used withspectra-commit
harrychuang/cursor-skills/.claude/skills/spectra-verify/SKILL.md
Verify implementation matches artifacts
harrychuang/cursor-skills/cross-platform-parity/SKILL.md
Export a lead-to-follower platform parity handoff pack after the lead platform's feature slice merges to its integration branch, or audit the follower platform against that pack before and after implementation. Derives the freeze point, change inventory, screen-by-state matrix, visual values, string ids, behavior contract, API/remote-config/event keys, shared component impact and declared platform differences from the merged diff and source code instead of narrative docs; project-specific paths and patterns come from a JSON project profile. Use whenever one platform's feature is handed to the other (iOS to Android or the reverse), the second platform must match an existing implementation, or a cross-platform parity report is requested; not for shared contract rules, feature planning or single-platform work.
harrychuang/cursor-skills/.cursor/skills/spectra-apply/SKILL.md
Implement or resume tasks from a Spectra change
Often used withspectra-commit
harrychuang/cursor-skills/.cursor/skills/spectra-archive/SKILL.md
Archive a completed change
Often used withspectra-commit
harrychuang/cursor-skills/.cursor/skills/spectra-audit/SKILL.md
Audit changed code for security sharp edges — dangerous defaults, type confusion, and silent failures
Often used withspectra-commit
harrychuang/cursor-skills/.cursor/skills/spectra-commit/SKILL.md
Commit files related to a specific Spectra change
harrychuang/cursor-skills/.cursor/skills/spectra-debug/SKILL.md
Systematically debug a problem using a four-phase workflow
Often used withspectra-commit
harrychuang/cursor-skills/.cursor/skills/spectra-discuss/SKILL.md
Have a focused discussion about a topic and reach a conclusion
Often used withspectra-commit
harrychuang/cursor-skills/.cursor/skills/spectra-ingest/SKILL.md
Update an existing Spectra change from external context
Often used withspectra-commit
harrychuang/cursor-skills/.cursor/skills/spectra-propose/SKILL.md
Create a change proposal with all required artifacts
Often used withspectra-commit
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.