Community写作与编辑github.com

dustinkeeton/wafflestack

🧇 One batter, every repo — reusable AI agent & skill definitions rendered into harness-native files (.claude/, .codex/, .agents/)

兼容平台Claude CodeCodex CLI~Cursor
npx skills add dustinkeeton/wafflestack

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

文档

Documentation Orchestration

When this skill is invoked, run the following pipeline:

Step 1: Architecture Audit

Spawn the general-purpose agent with this prompt:

Audit the current codebase for any changes since the docs were last updated. Read the existing machine docs (a single root AGENTS.md registry) and compare against the actual project. Produce a concise change report covering:

  • New or removed bundles, skills, agents, config keys, or CLI commands
  • Changed installer exports or template semantics (installer/lib/*.mjs)
  • bundle.yaml config declarations out of sync with placeholder usage
  • Rendered-output drift: node installer/cli.mjs doctor --allow-missing clean (committed render + lock in sync — re-render and commit after bundle edits); .gitignore still covers the deliberately-untracked renders (label-hook workflow, worktrees, .waffle/ overview docs)

Output ONLY the change report as structured text. Do NOT modify any files.

Step 2: Agent Documentation

Take the change report and spawn the docs-agent agent with this prompt:

Here is the architecture change report for the wafflestack codebase:

{step-1 output}

Update the machine docs — a single root AGENTS.md registry — to reflect the current state of the project. Read the actual source files to verify details — do not rely solely on the change report. Follow the docs-agent skill guidelines for format and structure.

Step 3: Human Documentation

After docs-agent completes, spawn the docs-human agent with this prompt:

The machine docs have just been updated. Update the human-facing documentation — DECISIONS.md, STATUS.md, and ARCHITECTURE.md at the repo root — to match.

Read the updated machine docs and the actual source to ensure accuracy. Follow the docs-human skill guidelines for format, structure, and its guardrails (owner-voiced docs are flagged, never rewritten).

Important

  • Each step must complete before the next begins — the output of each informs the next.
  • Step 1 is read-only — the audit agent only reports.
  • docs-agent and docs-human SHOULD modify their respective documentation files.

相关技能

steipete/notion

Notion CLI/API for pages, Markdown content, data sources, files, comments, search, Workers, and raw API calls.

community

affaan-m/seo

Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping.

community

affaan-m/brand-voice

Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.

community

affaan-m/crosspost

Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.

community

affaan-m/x-api

X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.

community

affaan-m/content-engine

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.

community