---
name: planu-context-assets
description: Create project-specific Planu rules or skills from the current app context so recurring standards and workflows become reusable agent guidance instead of MCP tool bloat.
triggers:
  - create project rules
  - create project skills
  - capture this workflow
  - make this a rule
  - make this a skill
  - codify this pattern
  - project context changed
  - app conventions
version: 1.0.0
---

# /planu-context-assets — Create Rules or Skills from App Context

## When to invoke

Use this skill when project context reveals a recurring convention, workflow, integration, domain rule, or implementation pattern that future agents should reuse.

Examples:

- A design system rule is discovered while implementing UI.
- A release or deployment workflow becomes stable.
- A legacy cleanup pattern repeats across modules.
- A domain invariant must never be violated.
- A framework-specific project convention is discovered during analysis.

## Decision rule

Create a **rule** when the guidance is mandatory and should constrain every future agent:

- architecture boundaries
- spec quality gates
- release policy
- BDD/SDD invariants
- security or data handling rules
- "never do X" / "always do Y" project standards

Create a **skill** when the guidance is an optional workflow invoked for a specific task:

- release workflow
- Figma implementation workflow
- legacy characterization workflow
- domain bundle generation
- integration setup
- migration playbook
- debugging or audit procedure

Do not create either when the information is one-off, speculative, or already covered by an existing rule/skill.

## Workflow

1. Inspect the current context and existing project assets:
   - `AGENTS.md`
   - `CLAUDE.md`
   - `.claude/rules/`
   - `.claude/skills/`
   - `.gemini/conventions.md`
   - `.gemini/skills/`
   - `.opencode/rules/`
   - `.opencode/skills/`
2. Decide whether the new asset is a rule, a skill, or nothing.
3. Keep the asset small and operational:
   - one purpose
   - explicit trigger
   - concrete steps or constraints
   - verification command when applicable
4. Use Planu host-aware tools:
   - `create_rule` for mandatory constraints
   - `create_skill` for reusable workflows
5. Use `host: "auto"` unless the user explicitly targets a host.
6. Prefer updating an existing Planu-owned asset over creating a duplicate.

## Quality bar

- Rules must be enforceable and written as constraints.
- Skills must describe when to invoke, what to inspect, what to do, and what output to produce.
- Do not reference legacy MCP tools that are not part of the 14-tool public core.
- Do not create broad "misc" skills.
- Do not preserve dead workflows "just in case".

## Output

Report:

- asset type: rule or skill
- asset name
- host target
- path or file updated
- why it should exist
- when it should trigger

