agentleFS
Sign inStart free
evgenii-studitskikhevgenii-studitskikh/Claude-Code-SaaS-Studio/.claude/skills/help/SKILL.md

help

Skill1 starsChanged 5 months agoMITView on GitHub

List all 23 studio skills grouped by phase, each with a one-line description. Run any time you need a map of what the studio can do.

76 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-stories, story-done and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 9 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 9 projects that use this

  • +10 more from lilangMax

The file

Create a free account to mount
Files
SKILL.md

Display the complete skill catalog for the SaaS Studio, organized by lifecycle phase, so the user can orient themselves and choose the right next action. Non-autonomous and read-only: it never writes files.

Phases

  1. Gather skill list — read all SKILL.md files under .claude/skills/*/ to collect live name: and description: values; use these rather than hardcoded text so the listing is always accurate.
  2. Group by phase — organize skills into six groups: (1) Navigation (start, help, studio-status, scope-check), (2) Product & UX (validate-idea, write-prd, map-flows, design-ui), (3) Engineering (setup-stack, design-architecture, design-schema, build-feature, code-review), (4) Billing (design-pricing, setup-billing), (5) Harden (qa-plan, test-setup, write-tests, security-audit, threat-model, compliance-check), (6) Infra & Launch (setup-deploy, launch-checklist).
  3. Format output — print each group as a heading with a numbered list of /skill-name — description entries. Keep descriptions to one line each. Indicate which skills write files vs. produce text-only output.
  4. Highlight current state — if docs/specs/ artifacts exist, note which phase the project appears to be in and which skills are most relevant right now.
  5. Invite action — ask if the user wants to jump to a specific skill or needs more detail on any entry.

Output

Formatted text listing only — no files written.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

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.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free