home / skills / interstellar-code / claud-skills / template-skill

template-skill skill

safe

/generic-claude-framework/skills/template-skill

This skill automates code scaffolding and documentation generation for JavaScript, TypeScript, PHP, Laravel, React, and Python projects.

This is most likely a fork of the template-skill skill from openclaw

npx playbooks add skill interstellar-code/claud-skills --skill template-skill

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

842 B

---
name: template-skill
description: Replace with description of the skill and when Claude should use it.
---

# Insert instructions below

## 🎨 **VISUAL OUTPUT FORMATTING**

**CRITICAL: All template-skill output MUST use the colored-output formatter skill!**

### Use Colored-Output Skill

**IMPORTANT: Use MINIMAL colored output (2-3 calls max) to prevent screen flickering!**

**Example formatted output (MINIMAL PATTERN):**
```bash
# START: Header only
bash .claude/skills/colored-output/color.sh skill-header "YOUR-SKILL-NAME" "Starting task..."

# MIDDLE: Regular text (no colored calls)
Processing data...
Performing operations...

# END: Result only
bash .claude/skills/colored-output/color.sh success "" "Task completed"
```

**WHY:** Each bash call creates a task in Claude CLI, causing screen flickering. Keep it minimal!

---

Overview

This skill provides a reusable template for building production-ready Claude Code integrations across multiple languages and frameworks. It standardizes structure, conventions, and output formatting so agents and skills behave consistently. It also enforces use of the colored-output formatter to produce minimal, stable CLI notifications.

How this skill works

The skill inspects the project layout and templates for agents, skills, and documentation patterns, then emits guidance and scaffolding to align new code with the framework. It injects or validates the required colored-output formatter usage and recommends where to place the minimal header and result calls. It flags deviations from the output pattern and suggests corrective edits.

When to use it

When creating a new Claude Code agent or skill scaffold
When standardizing project output behavior across languages (Python, JS, TS, PHP, Laravel, React)
When validating that CLI output uses minimal colored-output calls
When onboarding contributors to the framework conventions
When generating auto-documentation or cross-language templates

Best practices

Always call the colored-output formatter only at the start (header) and end (result) of a task to avoid flicker
Keep intermediate logs as plain text without color calls
Limit colored-output calls to 2–3 per run maximum
Place formatter invocations in the CLI entrypoint or top-level orchestration code
Include clear, short messages in header and result calls to aid automated parsing

Example use cases

Scaffold a new Python agent that follows repository conventions and emits a header and result using the colored-output skill
Validate existing skills for proper minimal colored output and suggest fixes
Generate cross-language templates (TypeScript, PHP, Laravel, React) that include correct formatter hooks
Onboard a new contributor by providing a template project demonstrating minimal colored CLI notifications
Run an automated check that flags extra colored-output calls to prevent screen flicker

FAQ

What exactly counts as a minimal colored-output call?

A minimal pattern uses a header call at task start and a single success/error call at task end, with plain text logs in between. Avoid color calls for intermediate steps.

Where should I place the formatter calls in my code?

Place the header call at the CLI entry or orchestration start and the result call at the top-level completion handler so they wrap the task lifecycle cleanly.