Skip to content

jabrena/plinth / skills/004-commands-installation

004-commands-installation

Verified

Use when you need to install the embedded project commands into command directories (.github/commands, .claude/commands, .cursor/command, .codex/commands), selecting the destination interactively and copying the embedded command definitions from project assets. This should trigger for requests such as Install embedded commands; Bootstrap .cursor/command; Bootstrap .claude/commands; Copy project commands; Install project command suite. Part of Plinth Toolkit

assets/commands/create-diagram.md

View on GitHub
---
description: 'Create an architecture or design diagram from selected source artifacts.'
argument-hint: '[source-artifact] [diagram-type]'
model: 'inherit'
agent: 'plinth-architect'
tools:
  - 'Read'
  - 'Write'
  - 'Edit'
metadata:
  author: 'Juan Antonio Breña Moral'
  version: '0.19.0'
---

# create-diagram

Create an architecture or design diagram that explains a selected system view.

## Usage

```text
/create-diagram <source-artifact> [<diagram-type>]
```

## Accepted Inputs

- Issue, approved design, ADR, specification, plan, or repository architecture
- Optional diagram type: sequence, class, state machine, ER, or C4
- Desired audience and level of detail

## Owning Agent

`@plinth-architect`

## Associated Skill

`033-architecture-diagrams`

## Workflow

1. Confirm the diagram purpose, audience, type, and scope.
2. Extract only the components and relationships needed for that view.
3. Generate the diagram source using the repository convention.
4. Check names and relationships against the source artifacts.
5. Report the diagram path and any assumptions.

## Output

- Diagram source for the selected architecture view
- Concise explanation of scope and assumptions
- Links to the source artifacts represented

## Safeguards

- Do not mix unrelated architecture views into one diagram.
- Do not invent components or interactions.
- Do not replace an existing diagram without reviewing its current purpose.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall