Skill

agent-context

Shared agent context — work attribution, safety rules, and development principles. Loaded by all plugin agents via skills: frontmatter.

Install

npx claudepluginhub shakestzd/htmlgraph --plugin htmlgraph

Tool Access

This skill uses the workspace's default tool permissions.

Preview

The orchestrator always provides the work item ID in your task prompt (e.g., "Feature: feat-580dc00b"). Use it:

SKILL.md

Similar Skills

kotlin-ktor-patterns

Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.

everything-claude-code

163.2k

deep-research

Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.

everything-claude-code

163.2k

inventory-demand-planning

Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.

everything-claude-code

163.2k

Stats

Parent Repo Stars3

Parent Repo Forks2

Last CommitApr 6, 2026

Actions

View Source View Plugin View on GitHub View README

Shared Agent Context

Work Attribution

The orchestrator always provides the work item ID in your task prompt (e.g., "Feature: feat-580dc00b"). Use it:

htmlgraph feature start <id> # or bug start / spike start

Rules:

Look for a feature/bug/spike ID in the task prompt first

If found, run start on it — do NOT create a new one

Only create a new work item if the prompt genuinely contains no ID

If htmlgraph is unavailable, proceed — attribution is not a blocker

Work Completion

When your task is done and quality gates pass:

Run htmlgraph feature complete <id> (or bug complete, spike complete)

Do this BEFORE reporting back to the orchestrator

If the CLI is unavailable, report completion — the orchestrator will handle it

Safety Rules

FORBIDDEN: Never edit .htmlgraph/ files directly. Use the CLI:

htmlgraph feature complete <id> not Edit(".htmlgraph/features/...")

htmlgraph bug create "title" not Write(".htmlgraph/bugs/...")

Plan YAML Updates

Plan YAML files (.htmlgraph/plans/*.yaml) are validated assets — never write them directly. Use the CLI to ensure valid structure:

Create: htmlgraph plan create-yaml "<title>"

Update: htmlgraph plan rewrite-yaml <plan-id> --file /tmp/updated.yaml

Validate: htmlgraph plan validate-yaml <plan-id>

The rewrite-yaml command validates schema, checks meta.id match, and writes atomically. Agent workflow: read plan → modify in memory → write to temp file → call rewrite-yaml.

Development Principles

DRY — check for existing utilities before creating new ones

SRP — one purpose per function/module

KISS — simplest solution that satisfies requirements

YAGNI — only implement what is needed now

Module limits: functions <50 lines, files <500 lines

Research existing libraries/packages before implementing from scratch

Check project dependencies before adding new ones

These principles are language-neutral and apply to any codebase.

Shared Agent Context

Work Attribution

The orchestrator always provides the work item ID in your task prompt (e.g., "Feature: feat-580dc00b"). Use it:

htmlgraph feature start <id>   # or bug start / spike start

Rules:

Look for a feature/bug/spike ID in the task prompt first
If found, run start on it — do NOT create a new one
Only create a new work item if the prompt genuinely contains no ID
If htmlgraph is unavailable, proceed — attribution is not a blocker

Work Completion

When your task is done and quality gates pass:

Run htmlgraph feature complete <id> (or bug complete, spike complete)
Do this BEFORE reporting back to the orchestrator
If the CLI is unavailable, report completion — the orchestrator will handle it

Safety Rules

FORBIDDEN: Never edit .htmlgraph/ files directly. Use the CLI:

htmlgraph feature complete <id> not Edit(".htmlgraph/features/...")
htmlgraph bug create "title" not Write(".htmlgraph/bugs/...")

Plan YAML Updates

Plan YAML files (.htmlgraph/plans/*.yaml) are validated assets — never write them directly. Use the CLI to ensure valid structure:

Create: htmlgraph plan create-yaml "<title>"
Update: htmlgraph plan rewrite-yaml <plan-id> --file /tmp/updated.yaml
Validate: htmlgraph plan validate-yaml <plan-id>

The rewrite-yaml command validates schema, checks meta.id match, and writes atomically. Agent workflow: read plan → modify in memory → write to temp file → call rewrite-yaml.

Development Principles

DRY — check for existing utilities before creating new ones
SRP — one purpose per function/module
KISS — simplest solution that satisfies requirements
YAGNI — only implement what is needed now
Module limits: functions <50 lines, files <500 lines
Research existing libraries/packages before implementing from scratch
Check project dependencies before adding new ones

These principles are language-neutral and apply to any codebase.