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

start

Skill1 starsChanged 5 months agoMITView on GitHub

Detect the project's current stage and route to the right first skill. Run at the very beginning of any new session. Shows the studio map and recommends the next action.

130 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-engine, team-audio 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.
  • CoralGameSkill

    setup-engine

    Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.

    Also in 13 projects that use this

  • CoralGameSkill

    team-audio

    Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

    Also in 13 projects that use this

  • 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 11 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 11 projects that use this

  • +5 more from CoralGame
  • +3 more from lilangMax

The file

Create a free account to mount
Files
SKILL.md

Orient the user within the SaaS Studio and route them to the correct starting skill based on where they are in the product lifecycle. Non-autonomous: asks one scoped question, presents options, waits for the user's choice before doing anything else.

Phases

  1. Probe stage — ask the user which best describes their situation: (a) no idea yet, (b) vague concept / rough idea, (c) clear design / written spec, (d) existing codebase to extend. Wait for their answer before continuing.
  2. Detect artifacts — check whether docs/specs/idea-validation.md, docs/specs/prd.md, docs/specs/architecture.md already exist to refine the routing; do not assume a stage if evidence contradicts the user's answer.
  3. Route — apply routing logic: (a/b) no idea or vague → recommend /validate-idea; (c) clear design → recommend /write-prd if no PRD exists, or /setup-stack if PRD exists; (d) existing code → recommend /studio-status first, then /write-prd if no PRD exists, else /design-architecture.
  4. Show the studio map — print a concise phase overview: Navigation skills → Product & UX → Engineering → Billing (/design-pricing → /setup-billing) → Harden (/qa-plan → /test-setup → /write-tests ; /security-audit · /threat-model · /compliance-check) → Infra & Launch, with a one-line description of each phase. Highlight where the user is right now.
  5. Confirm next step — present the recommended skill as a suggestion, not a command. Let the user accept, override, or ask questions.

Output

Routing guidance only — this skill writes no files. Ends by naming the exact slash command the user should run next.

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