메뉴
Use when the user asks for "an HTML" — an HTML document, page, report, explainer, announcement, week-in-review, summary, comparison, or any standalone HTML deliverable. Also use when converting a markdown report/notes into a shareable page. NOT for app UI components or pages inside a codebase (that's normal frontend work).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Audit a repo's agent-facing documentation layer and dispatch the right fix — instruction-file topology (AGENTS.md canonical? CLAUDE.md/GEMINI.md @import it?), always-loaded token cost, CodeMap freshness and line-number accuracy, broken pointers, changelog-vs-code version drift. Read-only; reports first, then offers remediation in dependency order. Use when asked to "check this repo", "audit the agent docs", "is my CLAUDE.md/AGENTS.md set up right", "are the docs stale", "check the code map", "health check this project", or when onboarding an unfamiliar repo and you want to know whether its docs can be trusted. Also on /repo-doctor. NOT for code review, tests, dependency or security audits.
Audit and rightsize CLAUDE.md / AGENTS.md and skills per Anthropic's Claude 5 context-engineering guidance (Thariq, 2026-07-24) — cut rules the model can judge, extract detail to on-demand files/skills, dedupe layers, and verify. Use when users mention slow /resume, CLAUDE.md being too long, reducing token usage, context optimization, rightsizing instructions, auditing CLAUDE.md, or following up on /doctor output. Triggers on "optimize CLAUDE.md", "rightsize my instructions", "my resume is slow", "CLAUDE.md is too big", "audit my CLAUDE.md", "apply the context-engineering rules", "slim down my instructions".
Sync Claude Code config (CLAUDE.md, agents, skills, commands, instructions, settings, statusline, guard hooks, plugins, MCP servers, CC version) AND the shared cross-CLI house-rules — canonical ~/.config/agents/AGENTS.md plus the per-CLI instruction files that @import it (CLAUDE.md, GEMINI.md) and Codex/Copilot/agy/Pi wiring — from THIS machine to any SSH-reachable host so every AI coding CLI works the same there. Discovers targets from ~/.ssh/config. Use on /sync-claude-config [host], or when asked to "sync claude config to <host>", "mirror my agents/skills to <machine>", "make Claude Code (or my agents) work the same on <host>". Push-only (local → remote); never copies credentials or machine state.
Restructure a project's (or the whole machine's) AI-agent instruction files so AGENTS.md is the single canonical guide that every coding CLI follows — Claude Code, Codex, Copilot, Antigravity/agy, Gemini, Pi — with CLAUDE.md and GEMINI.md reduced to thin @import pointers plus tool-specific extras. Use this whenever the user wants non-Claude agents to behave the same as Claude, mentions consolidating or unifying AGENTS.md / CLAUDE.md / GEMINI.md, says things like "make all my agents follow the same rules", "share my house rules across CLIs", "make Codex/Copilot/Gemini work like Claude", or wants to clean up duplicated/drifting instruction files. Works on the LOCAL project by default, then asks whether to also do the GLOBAL ~/.claude machine-wide setup. Trigger it even if the user doesn't name the skill.
Use when bumping a version, cutting a release, or when a CHANGELOG is stale, missing versions, or disagrees with the code — and before opening any PR, per the versioning rule in AGENTS.md. Also on /version-manager [check|backfill|release], or when the user says "bump the version", "cut a release", "the changelog is old". Auto-detects version locations in any stack (pyproject, package.json, VERSION file, module constants, README display) — no per-repo config.
Create a Discord post (announcement, release recap, changelog summary, community update) for the current project and save it as a markdown file under a Discord/ directory in the project root. Use this whenever the user asks to "create a Discord post", "write a Discord announcement", "make a Discord update", "post this to Discord", "draft a Discord message", or wants a community-facing summary of changes, a release, or news for a project — even if they don't say the word "skill". This skill only drafts and saves the post to a file; it never sends anything to Discord.
| name | html-doc |
| description | Use when the user asks for "an HTML" — an HTML document, page, report, explainer, announcement, week-in-review, summary, comparison, or any standalone HTML deliverable. Also use when converting a markdown report/notes into a shareable page. NOT for app UI components or pages inside a codebase (that's normal frontend work). |
Produce a self-contained, light/dark-themed, editorial-quality HTML document in the ChameleonLabs house style. One file, no build step, looks designed — never generic AI output.
Start from template.html in this skill's directory. It already contains the theme system, fonts, masthead, toggle, and footer. Replace the placeholder content; don't rebuild the scaffolding from scratch.
:root holds the document's default palette, [data-theme="light"] / [data-theme="dark"] holds the other. Include color-scheme in each. No hardcoded colors outside the variable blocks (glows/tints via vars too).</head>, so no flash) reads localStorage key cl.docs.theme, falls back to prefers-color-scheme, sets data-theme on <html>. A ☾ dark / ☀ light pill button in the kicker toggles and writes back to the same key — all CL docs share it.https://chameleonlabs.ai and https://discord.gg/chameleonlabs in the kicker AND footer. Add topic-relevant links (GitHub repos, companion docs) where they help — e.g. the Agent Spawner repo is https://github.com/Chameleon-Labs-LLC/agent-spawner.date '+%Y-%m-%d'. Plain language for mixed-experience readers; spell out jargon on first use.Notes/), filename <slug>-YYYY-MM-DD.html. Send with SendUserFile. Offer to commit.Masthead kicker (mono, uppercase, ◆ brand mark) → big Fraunces headline with an italic accent word → dek paragraph. Then: stat band, announcement banner with pulsing dot, numbered 01 / section heads, day-by-day timeline, definition card grids, top-to-bottom flow diagrams (TB, never LR), roster tables with badges, guardrail card grids, pull quotes, three-tier "start here" columns. Footer: brand links · companion link · "Compiled YYYY-MM-DD".
| Mistake | Fix |
|---|---|
| System/Inter fonts | Google Fonts, characterful pairing (req. 4) |
| Only one theme works | Test toggle both ways; every color must come from a var |
| New localStorage key per doc | Always cl.docs.theme |
| Theme script at end of body | Must be in <head> or first paint flashes |
| Invented stats/dates | Real data only; date for timestamps |
| Left-to-right flow diagrams | Top-to-bottom (TB) |
| Dumping the file silently | SendUserFile + offer commit |