agentleFS
winchxyzwinchxyz/idea-to-build/.claude/skills/profile/SKILL.md

profile

Skill9 starsChanged 5 months agoMITView on GitHub

Switch the idea-to-build coordinator to a domain profile — general, startup, tech-architecture, content-strategy, product-roadmap, or personal-decisions. Use when the user types "/profile startup" (or any profile name) or asks to switch, activate, or change the brainstorming profile.

30 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use apply, coverage and 5 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.
  • rhowardstoneSkill

    apply

    Research-backed job application workflow emphasizing relationship-building over mass applications

    Also in 3 projects that use this

  • PydanticSkill

    coverage

    Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.

    Also in 3 projects that use this

  • dragonflydbSkill

    benchmark

    Benchmark Dragonfly (and compare against Valkey/Redis) on local or remote cloud instances, then produce a performance + memory report with charts and a raw-data appendix. Use this whenever the user runs /benchmark, or asks to benchmark / load-test / measure throughput, QPS, latency, or memory efficiency of Dragonfly or another Redis-compatible server, to compare Dragonfly vs Valkey or Redis, or to generate a benchmark report. Trigger it even when the user just describes the goal ("see how fast Dragonfly is on this box", "compare memory per key vs Valkey") without saying the word "benchmark".

    Also in 3 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    docs

    Also in 3 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the name is missing or not in that list, list the valid profiles and ask which one — do not guess.

    line 15
  2. Very specific:

    If the user included an idea in the same message (e.g.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/profile — switch domain profile

The user wants to activate a domain profile for the idea-to-build coordinator. A profile overrides the coordinator's defaults inside each phase (which frameworks it reaches for, which questions it asks) — it does not skip phases or change the 6-phase flow.

Steps

  1. Read the coordinator spec core/CLAUDE.md (if you haven't already in this session) so you stay in the coordinator role.
  2. Determine the requested profile from what the user provided after /profile (as a slash command, $ARGUMENTS; e.g. /profile startup → startup). Valid names: general, startup, personal-project, exploration, tech-architecture, content-strategy, product-roadmap, personal-decisions.
  3. If the name is missing or not in that list, list the valid profiles and ask which one — do not guess.
  4. Read profiles/<name>.md from the repository root and adopt it as the active profile, layered on top of core/CLAUDE.md.
  5. Confirm in one line: Profile: <name>.
  6. If the user included an idea in the same message (e.g. /profile startup I want to build X), begin Phase 1 — Understanding on that idea, through the profile's lens: restate the goal in your own words, then ask only the questions needed to close real gaps.

Rules

  • Stay in the coordinator role. Do not jump to building or generating solutions.
  • The profile changes the lens, not the process — keep phase-explicit communication and the commit-signal gate between phases.
  • Honor cross-project isolation: do not import context from other projects unless the user invokes it.

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.