Skip to content

aiskillstore/marketplace / skills/0xdarkmatter/claude-code-templates

claude-code-templates

Unverified

Boilerplate templates for Claude Code extensions. Triggers on: create agent, new skill, command template, hook script, extension scaffold.

FileKindSize
SKILL.mdskill md3.0 KB
assets/agent-template.mdmarkdown1.9 KB
assets/command-template.mdmarkdown1.5 KB
assets/hook-script.shscript2.2 KB
assets/skill-template.mdmarkdown3.8 KB
skill-report.jsonconfig66.7 KB

assets/command-template.md

View on GitHub
---
name: command-name
description: "What this command does in one sentence."
---

# /command-name

Brief description of the command's purpose.

## Usage

```
/command-name [options] [arguments]
```

## Execution Flow

```
/command-name
    │
    ├── Step 1: [Action]
    │   └── [Details]
    │
    ├── Step 2: [Action]
    │   └── [Details]
    │
    └── Step 3: [Action]
        └── [Details]
```

## Instructions

### Step 1: [Action Name]

[Detailed instructions for this step]

- Sub-step A
- Sub-step B

### Step 2: [Action Name]

[Detailed instructions for this step]

### Step 3: [Action Name]

[Detailed instructions for this step]

## Options

| Flag | Description | Default |
|------|-------------|---------|
| `--flag1` | Description | value |
| `--flag2` | Description | value |

## Examples

### Basic Usage

```
/command-name
```

### With Options

```
/command-name --flag1 value
```

### Full Example

```
/command-name --flag1 value --flag2 value argument
```

## Output

[Description of what the command produces]

<!--
USAGE INSTRUCTIONS:

1. Copy to ~/.claude/commands/your-command.md or .claude/commands/
2. Replace all [placeholders] with your content
3. Ensure filename matches the `name` field
4. Keep execution flow clear and scannable
5. Test by typing /your-command in Claude

TIPS:
- Execution flow should be visual and easy to follow
- Each step should be actionable
- Include real examples users can copy
- Document all options with defaults
-->
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: 471kUpdated 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