Explore skills

Writes new worldbuilding content: civilizations, characters, locations, factions, events, languages, or narrative elements. Use when creating new entries, expanding existing ones, or when user says "create", "write", "add", "flesh out", "build", or "expand" for any non-science content. Does NOT write science files — use /writing-science for that.

Writes new science files following academic prose standards: third-person voice, present tense for laws, in-universe terminology, consistent equation formatting, citation format. Use when creating new physics, chemistry, biology, or science files, expanding existing science content, or when user says "write", "create", "draft", "formalize", or "derive" in a science context. Does NOT write civiliza

Amazon''s Working Backwards product development method based on Colin Bryar and Bill Carr''s "Working Backwards". Use this skill whenever the user is discussing a new product, feature, pitch, or launch narrative — even if they do not explicitly say "PR/FAQ," "press release," or "working backwards." Triggers include: (1) writing or reviewing a PR/FAQ for a new product or feature, (2) drafting the l

This skill should be used when the user wants to distill their personal writing style, techniques, and thought patterns from their past articles (especially WeChat public account posts) into a reusable writing DNA profile. Use this skill to analyze writing samples, extract style fingerprints through multi-layer validation, and generate new content that faithfully replicates the user's unique voice

Full project context setup and session management skill. Use this when starting a new project, onboarding onto an existing codebase, resuming work after a session gap, ending a session and wanting to save progress, or when context is running low mid-session. Sets up a docs/context/ system that any AI tool can read (Claude, Codex, Cursor, Windsurf). Three modes: SETUP (first time), RESUME (session

Automated blog content pipeline. Research, write, generate images, create WordPress draft, and prepare social media versions overnight. Wake up to a complete content package ready to publish.

Use this skill for any documentation task: writing or updating READMEs, creating docstrings, authoring runbooks, writing API documentation, creating onboarding guides, maintaining changelogs, writing architecture docs, or any task where the deliverable is written documentation. Triggers on: "write documentation", "document this", "write a README", "add docstrings", "write a runbook", "API docs", "

10-point framework for optimizing written content for audio/voice delivery. Blog audio, training modules, video scripts, podcast content, voiceover copy.

Maintain the Zensical-powered documentation site — nav ordering in zensical.toml, the docs GitHub Pages workflow, CSS and JS assets, and link/anchor integrity across docs/**/*.md. Sibling of /techne:docsync (which only verifies prose claims against code). Use when the user wants the site itself audited — config, deploy pipeline, theming, assets, cross-page links — rather than content accuracy.

Check a documentation file for drift against the actual codebase — CLI commands, file paths, config keys, function signatures, version numbers, environment variables — and propose corrections. Use when the user wants to audit README.md, docs/*.md, or similar for claims that no longer match reality. Drift usually comes from refactors that forgot to update the docs.

Rewrite docstrings and comments by reading the actual implementation, call sites, and tests — produce grounded, factual prose instead of deleting slop. Sibling of /techne:deslop. Use when the user wants to replace overhyped or hallucinated documentation with accurate one- or two-line descriptions derived from what the code actually does.

Define the reader/customer avatar, painful current state, desired outcome, transformation bridge, objections, and proof needed before writing profile copy, posts, articles, landing pages, or visual concepts.