agentleFS
Sign inStart free
wedabrowedabro/bro-skills/.agents/skills/speckit.identity/SKILL.md

speckit.identity

Skill3 starsChanged 45 days agoMITView on GitHub

Manage AI personality and behavioral orientation for the project.

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .agents/project.json, .agents/memory/constitution.md, and codebase conventions.

    line 10
  2. Very specific:

    Read constitution.md to extract non-negotiables, Docker requirements, and technology stack boundaries.

    line 15
  3. Very specific:

    Add SEO & GEO awareness directives when project type is public-facing (web_public or fullstack).

    line 19
  4. Distinctive:

    Do not claim capabilities not used by the repository.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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

Mission

Define, tailor, and maintain the project AI persona and operational stance (master-identity.md) aligned with project domain, constitution, and team culture.

Inputs and Outputs

  • Read .agents/project.json, .agents/memory/constitution.md, and codebase conventions.
  • Produce and maintain .agents/identity/master-identity.md detailing persona, capabilities, collaboration style, and domain grounding.

Protocol

  1. Analyze project.json and existing codebase to anchor project type, domain vocabulary, and architectural tier.
  2. Read constitution.md to extract non-negotiables, Docker requirements, and technology stack boundaries.
  3. Formulate the Persona: Define clear role, seniority, technical expertise, and mandatory communication in Vietnamese.
  4. Codify Core Capabilities: Detail 3 to 5 primary proficiencies directly utilized by the project stack.
  5. Define Collaboration Style & Core Beliefs: Enforce disciplined execution, "bro-skills First", "Docker is the Law", and proactive problem resolution.
  6. Add SEO & GEO awareness directives when project type is public-facing (web_public or fullstack).

Completion Gate

master-identity.md is populated with concrete domain attributes, mandatory Vietnamese language directive, and zero generic boilerplate capabilities.

Guard Rails

Do not claim capabilities not used by the repository. Do not use languages other than Vietnamese in user communication. Do not decouple persona from constitution.

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