ai-firstify
Analyze, re-engineer, or bootstrap projects to align with AI-first design principles. Use when asked to review, audit, improve, 'ai-firstify', or start a new project. Performs deep analysis across 7 dimensions, actively restructures existing projects, or guides new project setup through discovery questions. Based on the 9 design principles and 7 design patterns from the TechWolf AI-First Bootcamp.
git clone --depth 1 https://github.com/techwolf-ai/ai-first-toolkit /tmp/ai-firstify && cp -r /tmp/ai-firstify/plugins/ai-firstify/skills/ai-firstify ~/.claude/skills/ai-firstifySKILL.md
# AI-Firstify Analyze and re-engineer projects to align with AI-first design principles. ## Trigger Use this skill when asked to: - **Audit mode** (read-only): "review", "audit", "analyze", "check", "assess" - **Re-Engineer mode** (active changes): "ai-firstify", "fix", "improve", "re-engineer", "transform" - **Bootstrap mode** (new project): "start", "new project", "bootstrap", "set up", "build from scratch" ## Mode 1: Audit (Read-Only Analysis) Perform a comprehensive read-only analysis across 7 dimensions. Output a scored report with recommendations. Do NOT modify any files. Read **references/mode-audit.md** for the full audit procedure and dimension checklist. ## Mode 2: Re-Engineer (Active Transformation) First, perform the full audit (Mode 1). Then actively fix issues in 7 phases: foundation, de-agentification, skill extraction, complexity reduction, context hygiene, safety hardening, workflow optimization. Read **references/mode-reengineer.md** for the full re-engineering procedure. ## Mode 3: Bootstrap (New Project Setup) Guide the user through setting up a new AI-first project from scratch. Interactive: ask discovery questions, recommend architecture, scaffold, and test. Read **references/mode-bootstrap.md** for the full bootstrap procedure. ## Reference Files Domain knowledge (load on demand per dimension): - **references/principles.md**: All 9 AI-first design principles in depth - **references/patterns.md**: All 7 design patterns with implementation guidance - **references/anti-patterns.md**: Common mistakes with detection patterns and fixes - **references/skill-architecture.md**: How to structure skills, sub-agents, and workflows - **references/project-structure.md**: Ideal project layouts, CLAUDE.md templates, .gitignore - **references/assessment-rubric.md**: Scoring criteria and report template Load the relevant reference file for the dimension you are currently analyzing. Do not load all references at once. Use progressive disclosure. ## Tools - **scripts/validate-report.sh**: Validates that a generated assessment report has all required sections, dimensions, and scores
Find context from past Claude Code (CLI) and Claude Cowork (desktop) sessions on this Mac. Use when the user wants to recall something they did before but can't find it , phrasings like "where did I work on X", "find that session where I…", "when did I last do Y", "pull up the conversation about Z", "that time I built/tried/discussed …". Searches by kind (code/cowork), time range, title, working directory, or free-text content across all transcripts.
Mine the user's Claude Code + Cowork session history into a structured task profile, what they do with AI, how often, how successfully where friction lives, then propose atomic skills that would reduce iteration. Use when the user asks to "analyse my Claude use", "build a task profile", "what tasks do I do with Claude", "where am I spending tokens", "what skills would help me", or mentions reviewing past sessions for patterns. Produces profile.csv (shareable), explorer.html (personal coaching view with AI-first principle comparison + token-spend chart), and skill-proposals.md.
Personal diagnosis of where your Claude Code + Cowork spend goes. Reads local transcripts, prints your conversation length distribution, marathon share, cache rebuild costs, and per-project diagnosis (good projects and problem projects) right in the terminal. Then offers a deeper dive that fans out parallel Haiku subagents over your most expensive (and most efficient) sessions and writes a tight Markdown report. Use when the user asks "why is my Claude spend so high", "where am I burning tokens", "diagnose my Claude habits", "audit my Claude usage", or asks for a personal token-cost diagnosis.
Analyze engagement patterns across published posts to identify what works. Use when asked to review performance, find successful patterns, or optimize future content.
Generate LinkedIn post ideas from external sources (files, URLs, research). Use when the user provides source material (PDFs, URLs, articles) to brainstorm topics. NOT for writing or developing drafts - use write-linkedin-post instead.
Generate opinion piece ideas from recent LinkedIn posts (last 30 days). Use when asked to find opinion topics, brainstorm article ideas, or cross-pollinate content between LinkedIn and opinion pieces.
Entry point for the TechWolf content-studio plugin. Use to understand the workflow, pick the right content skill, or start setup for a new author/repository.
Set up a new content studio for a person. Copies the plugin template, adapts it to the person's voice, themes, and content types through interactive discovery. Use when asked to create a content studio for someone new.