Jacob Krajewski Tools

All tools
Claude Code · 108 skills

Skills I actually use, packaged up.

based-stack is a library of 108 Claude Code skills — the mental models and playbooks I reach for every day. Strategy, product, marketing, sales, UX, engineering, and workflow discipline. Load a skill to shape Claude's thinking, or chain several together for a two-pass workflow.

What's inside

  • 41 knowledge frameworks — StoryBrand, Made to Stick, Blue Ocean, JTBD, Lean Startup, Influence, Shape Up, Clean Architecture, and more. Load one to shape how Claude approaches a problem.
  • 32 task checklists — CRO audits, SEO audits, copywriting, schema markup, signup flows, cold email, referral programs, and writing-voice for prose in my published style. Concrete "do this" skills with a fixed output.
  • 6 process orchestrators — scripts that drive their own exploration: codebase analysis, deepthink, decision critique, refactor audit, problem analysis, prompt engineering.
  • 20 workflow discipline skills — planning, executing plans, TDD, systematic debugging, code review, worktrees, verification before completion, dispatching parallel agents, grill-me for stress-testing designs, and init-vault for scaffolding new Obsidian vaults.
  • 9 platform tools — PDF/DOCX/PPTX/XLSX ops, schedule, skill-creator, update-config, keybindings, doc-sync, arxiv-to-md, cc-history, claude-api.
  • 1 slash command/update-workstate detects meaningful changes in the current session and updates WORKSTATE / CHANGELOG / ARCHITECTURE for every tracked project. Two-phase: detect first, early-exit if nothing qualifies.

Install

Each subfolder is a self-contained skill with its own SKILL.md. Clone the repo, then symlink every skill into Claude Code's global skills directory:

  1. Clone the repo anywhere on disk. git clone https://github.com/sachio222/based-stack.git ~/dev/based-stack
  2. Symlink the skills into ~/.claude/skills/ so Claude Code picks them up globally. mkdir -p ~/.claude/skills && cd ~/dev/based-stack && for d in */; do ln -sf "$PWD/${d%/}" ~/.claude/skills/${d%/}; done
  3. Invoke a skill in Claude Code with its name — e.g. /storybrand-messaging or /jobs-to-be-done. Claude loads the skill's framework and reference files.

The full skills list

All 105 skills, grouped by kind. Expand a section to see every skill and when to reach for it.

1 · Knowledge frameworks (41)

Load a mental model to shape how Claude approaches a problem — before executing anything.

Marketing & messaging

  • storybrand-messaging — brand messaging, elevator pitch, landing page copy.
  • made-to-stick — memorable messaging, taglines, SUCCESs checklist.
  • contagious — word-of-mouth, virality, STEPPS framework.
  • influence-psychology — social proof, ethical persuasion (Cialdini).
  • marketing-psychology — cognitive biases applied to marketing decisions.
  • one-page-marketing — full plan: target, USP, lead nurture, CLV.
  • scorecard-marketing — quiz funnels, assessments, score-based segments.
  • cro-methodology — A/B tests, objection handling, funnel mapping.

Sales & offers

  • hundred-million-offers — pricing, irresistible offers, guarantees.
  • predictable-revenue — outbound B2B, SDR process, pipeline building.
  • negotiation — contract terms, tactical empathy (Voss).

Strategy & positioning

  • obviously-awesome — product positioning, market category.
  • crossing-the-chasm — tech adoption, beachhead segments.
  • blue-ocean-strategy — uncontested market, ERRC framework.
  • traction-eos — V/TO, quarterly rocks, L10 meetings.
  • decisive — decision-making (WRAP framework).

Product & discovery

  • jobs-to-be-done — customer discovery, PMF, JTBD interviews.
  • mom-test — customer interviews without leading questions.
  • lean-startup — MVP scoping, validated learning, pivot/persevere.
  • continuous-discovery — weekly touchpoints, opportunity trees.
  • design-sprint — 5-day prototype-and-test cycle.
  • inspired-product — empowered teams, dual-track, product vision.
  • design-everyday-things — affordances, signifiers, error prevention.
  • testing-business-ideas — 44 experiment types, pretotyping.

Project management

  • shape-up — 6-week cycles, appetite-based scoping, hill charts.

UX & design

  • hooked-ux — habit loops, engagement, variable rewards.
  • improve-retention — activation, onboarding, B=MAP behavior design.
  • ux-heuristics — Nielsen's 10, usability audits.
  • lean-ux — hypothesis-driven design, rapid experimentation.
  • microinteractions — animations, feedback, state changes.
  • top-design — layout, visual hierarchy, grids.
  • refactoring-ui — spacing, color, typography fixes.
  • web-typography — font pairing, type scale, readability.
  • ios-hig-design — iOS patterns and HIG compliance.

Team & culture

  • drive-motivation — intrinsic motivation, autonomy/mastery/purpose.
  • culture-code — team culture, psychological safety, onboarding.

Engineering

  • clean-code — readability, naming, formatting.
  • clean-architecture — dependency rules, layered architecture.
  • domain-driven-design — bounded contexts, aggregates, ubiquitous language.
  • pragmatic-programmer — general engineering philosophy.
  • refactoring-patterns — code smells, systematic refactoring.
  • software-design-philosophy — module design, complexity management.
  • ddia-systems — distributed systems, replication, partitioning.
  • system-design — system design interviews and architecture.
  • high-perf-browser — browser performance and rendering.
  • release-it — production stability, circuit breakers.
2 · Task checklists (32)

Specific step-by-step workflows to execute. Load these to produce a deliverable or audit against a checklist.

Context & foundation

  • product-marketing-context — run first. Creates the product context doc.
  • customer-research — ICP, personas, VOC, review mining.

Writing & copy

  • copywriting — homepage, landing, pricing, feature, about.
  • copy-editing — tighten, sharpen, fix awkward reads.
  • content-strategy — topic clusters, editorial calendar.
  • social-content — LinkedIn, Instagram, TikTok, X.
  • ad-creative — headlines and variations for Google / Meta / LinkedIn.
  • cold-email — B2B outreach emails and sequences.
  • email-sequence — drip, nurture, welcome, lifecycle.
  • competitor-alternatives — "vs" pages, comparison content.
  • writing-voice — write prose in my published voice (conversational-technical, second-person, rhetorical-question openers).

CRO & conversion

  • page-cro — audit any marketing page.
  • form-cro — lead capture, contact, demo request forms.
  • signup-flow-cro — registration and trial activation flows.
  • onboarding-cro — post-signup onboarding and time-to-value.
  • popup-cro — popups, modals, exit intent, sticky bars.
  • paywall-upgrade-cro — paywalls, upgrade screens, feature gates.
  • ab-test-setup — hypotheses, variants, statistical significance.
  • churn-prevention — cancellation flows, save offers, win-back.

SEO & analytics

  • seo-audit — technical SEO, on-page, Core Web Vitals.
  • ai-seo — ChatGPT, Perplexity, AI Overviews (GEO / AEO / LLMO).
  • schema-markup — JSON-LD, FAQ, product, rich snippets.
  • programmatic-seo — location, comparison, directory pages at scale.
  • site-architecture — hierarchy, navigation, internal linking.
  • analytics-tracking — GA4, GTM, conversion tracking.

Strategy & growth

  • pricing-strategy — packaging, tiers, freemium, willingness to pay.
  • launch-strategy — GTM, early access, waitlists.
  • marketing-ideas — brainstorm tactics when stuck.
  • lead-magnets — ebooks, checklists, templates, gated content.
  • free-tool-strategy — calculators, graders, audit tools.
  • referral-program — referrals, affiliates, ambassadors.
  • paid-ads — Google, Meta, LinkedIn campaign strategy.
  • revops — lead scoring, routing, MQL/SQL, handoff.
  • sales-enablement — pitch decks, one-pagers, demo scripts.
3 · Process orchestrators (6)

Python scripts that take over session flow. Invoke immediately — they orchestrate their own exploration.

  • codebase-analysis — repo orientation, architecture comprehension.
  • decision-critic — stress-test decisions and reasoning.
  • deepthink — structured reasoning for open-ended questions.
  • problem-analysis — root cause investigation.
  • prompt-engineer — prompt optimization.
  • refactor — refactoring analysis, technical debt review.
4 · Workflow discipline (20)

Skills that enforce a specific development practice. Load before starting the activity.

  • brainstorming — before any creative or feature work.
  • grill-me — stress-test a plan or design by answering interview-style questions one at a time.
  • init-vault — scaffold a new Obsidian vault with the canonical WORKSTATE / ARCHITECTURE / CHANGELOG / README / CLAUDE.md layout.
  • writing-plans — when you have a spec for a multi-step task.
  • executing-plans — execute a written plan with review checkpoints.
  • subagent-driven-development — independent tasks in the current session.
  • dispatching-parallel-agents — 2+ independent tasks without shared state.
  • test-driven-development — before writing implementation code.
  • systematic-debugging — any bug, test failure, unexpected behavior.
  • requesting-code-review — completing tasks, before merging.
  • receiving-code-review — processing review feedback.
  • verification-before-completion — before claiming work is done.
  • finishing-a-development-branch — deciding how to integrate.
  • using-git-worktrees — feature work needing isolation.
  • writing-skills — creating, editing, verifying skills.
  • using-superpowers — session start: how to find and use skills.
  • context-engineering — structuring context and memory for LLMs.
  • incoherence — detect drift between docs / code / specs.
  • simplify — review changed code for reuse, quality, efficiency.
  • planner — interactive planning and execution for complex tasks.
5 · Platform tools (9)

Utility skills for file formats, scheduling, configuration, and integrations.

  • update-config — Claude Code harness: hooks, permissions, settings.
  • keybindings-help — customize keyboard shortcuts.
  • loop — run a prompt or slash command on a recurring interval.
  • schedule — scheduled remote agents on cron.
  • claude-api — build apps with the Claude API or SDK.
  • cc-history — analyze Claude Code conversation history.
  • doc-sync — synchronize docs across a repository.
  • arxiv-to-md — convert arXiv papers to LLM-consumable markdown.
  • Plus Anthropic's built-in skills for PDF, DOCX, PPTX, XLSX, schedule, and skill-creator.
6 · Slash commands (1)

User-invokable slash commands — not SKILL.md-based, but installed into ~/.claude/commands/ and run directly in the parent session.

  • /update-workstate — detect meaningful changes in the current session and update WORKSTATE.md / CHANGELOG.md / ARCHITECTURE.md for every tracked project under ~/Agents/Workspaces/ and ~/dev/. Two-phase: cheap detect-first check (early-exits if nothing qualifies), then conservative classify and update. Sidesteps the reliability issues of earlier SessionEnd and Stop hook approaches (both deprecated) by running synchronously in the session you're already in.

Using it

Two patterns cover most of my use.

  • Two-pass workflow. First load a framework skill (pass 1) to shape Claude's approach — e.g. /storybrand-messaging. Then load a task checklist (pass 2) to execute — e.g. /copywriting. The framework shapes the output; the checklist produces it.
  • Common combos. Launch strategy = /jobs-to-be-done + /obviously-awesome + /launch-strategy. CRO audit = /cro-methodology + /ux-heuristics + /page-cro. Debugging = /problem-analysis + /systematic-debugging.

Full cross-references, orchestration patterns, and subagent recommendations live in the repo's skills-index.

Credits

Special thanks to Avery Lorenzato for curating much of this list.

Source on GitHub Full skills index Report a bug