Persona dev

Skill kickinrad/personas-framework/skills/persona-dev

Use when the user asks to create, evolve, reconcile, or activate a persona folder, or connect an approved capability to it.From its SKILL.md

Install

npx -y skills add kickinrad/personas-framework --skill persona-dev

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.3 KB, as published. Nobody here has run it

Develop a persona

A persona is a readable folder. Keep its portable definition, runtime adapters, private local context, and external knowledge sources distinct.

Create

Discover the desired name, role, outcomes, voice, boundaries, workflows, local context, and target runtimes. Ask only questions that materially change the folder.
Read the templates in assets/. Read references/environments.md when choosing a home across native, WSL, Windows, Desktop, or Cowork. Read references/launch-flags.md when configuring a Claude launcher. Read references/research-toolkit.md when the persona needs a new capability.
Present one complete folder plan. Include the portable AGENTS.md, importing CLAUDE.md, shared skills, minimal native settings, ignored local context, and any requested integration. Write nothing before approval.
After approval, create the folder directly with normal file operations:
- AGENTS.md owns identity, voice, role, boundaries, and shared doctrine;
- CLAUDE.md imports AGENTS.md for Claude Code;
- .claude/settings.json and .codex/config.toml contain minimal native project settings;
- skills/ contains portable role workflows;
- user/ contains optional ignored profile and explicit memory.
Replace every template placeholder with reviewed persona-specific content. Do not leave generic role filler in a finished persona.
Create no hook merely for symmetry, reminders, framework drift, repository visibility, or memory simulation.
Keep everything tracked in Git safe to publish. Never put profile, memory, local settings, connections, or credentials in tracked files.
Inspect the resulting tree and exact diff. Confirm AGENTS.md is the only resident persona authority and CLAUDE.md imports it.
Ask separately before plugin installation, repository creation, external connection, publishing, or changes to an existing persona's private data.

Evolve or reconcile

For an existing persona, inspect its folder first and edit only the owning surface; self-improve's "Route the change" list owns content routing. Prefer an existing capability over a new wrapper. Read references/lifecycle-meta.md when ownership between those surfaces is unclear.

Compare existing folders with the current portable contract, classify each difference as adapter drift, persona-owned customization, obsolete machinery, or ambiguity, and show the reconciliation plan before writing. Preserve persona-owned meaning and optional ignored user/ context.

Activate native adapters

Use scripts/persona-native-sync.py --persona PATH --runtime claude|codex|all to validate and report native-agent drift. Add --apply only after explicit approval to install runtime state. The helper generates adapters that read the live absolute AGENTS.md; it never copies identity prose. It reports the Claude path-access requirement and never changes global Claude permissions.

Verify

Read the finished folder as a user would. Check that it is understandable, contains no duplicated doctrine, keeps private state ignored, and provides equivalent Claude and Codex entry paths. Run the framework test suite only when changing the framework itself.