From geopol-sim
Edit the simulation participants in a workspace — actor persona briefs (snowglobe-style templates) or council-member panel models (council-style templates). Use when the user wants to "update actors", "edit personas", "swap a model in the panel", "add an actor", or "change the council members". Sentinel-aware: dispatches based on whether the workspace template supports actor editing.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin geopol-simThis skill is limited to using the following tools:
Two very different operations live behind one user-facing concept ("the participants in the simulation"):
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes multiple pages for keyword overlap, SEO cannibalization risks, and content duplication. Suggests differentiation, consolidation, and resolution strategies when reviewing similar content.
Share bugs, ideas, or general feedback.
Two very different operations live behind one user-facing concept ("the participants in the simulation"):
geopol/actors/*.md). Editing means rewriting briefs, adding new ones, or removing ones.cat <workspace>/.template-id. Look up the template in templates/registry.json.supports_actor_edit:
true — open the directory at actors_path (e.g. geopol/actors/). List existing briefs. Ask what the user wants to do: edit one, add a new persona, remove one, or bulk-restructure. For new personas, follow the field structure of existing briefs in that template (don't invent a new format). For edits, preserve frontmatter if the upstream uses it.false — explain that this template has no editable actor sim. The participants are the council-member LLMs, configured at run time. Ask if the user wants to update the model panel for future runs. If yes:
--council-members default).scenario.md (or a panel.txt if simpler), so run-simulation can read it back and pass --council-members automatically.reports/<timestamp>/). Past runs are immutable history.