Lvtd Skills

Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs). Use when listing books, searching/filtering library records, reading/updating metadata, adding/removing formats, exporting books, maintaining custom columns, running library checks, managing FTS indexing/search, or creating catalogs/backups from a Calibre library.

Use when adding, changing, testing, or debugging Django Q2 background tasks, scheduled jobs, qcluster workers, Redis broker configuration, or ORM broker fallback in this generated Django SaaS app.

Build and review HTMX interactions in Django server-rendered projects, especially generated django-saas-starter apps. Use when adding hx attributes, partial template responses, request.htmx branching, django-htmx response headers, forms, swaps, triggers, redirects, polling, boosted links or forms, or coordinating HTMX with Alpine.js local state.

Design and pressure-test useful nonfiction book promises, scopes, recommendation loops, and takeaway-first tables of contents before drafting. Use when planning, outlining, scoping, restructuring, validating, or testing a practical book, guide, manual, course-like book, or other reader-outcome-focused long-form nonfiction.

Use when adding, changing, testing, or debugging Cookiecutter templates, including cookiecutter.json variables, Jinja-rendered files, hooks, _copy_without_render, optional feature cleanup, and generated-project validation.

Use when adding, changing, deploying, testing, or debugging FastMCP MCP servers in existing Django apps, including ASGI mounting, stdio or sidecar servers, Django ORM access from MCP tools, auth and permissions, Streamable HTTP deployment, and MCP client tests.

Use when adding, changing, or debugging Alpine.js behavior in this Django SaaS Starter project, especially in Django templates that may also use HTMX partial updates.

Review traction experiment results and recommend whether to double down, iterate, repeat Bullseye, or pivot. Use when analyzing growth test data, comparing channel performance, deciding if a channel moved the needle, or reassessing startup traction strategy.

Design faster, clearer Django test data and test structure with factories, setUpTestData, SimpleTestCase/TestCase choices, fixture-file cleanup, query optimization, and unit-vs-integration boundaries. Use when Django tests create too much data, rely on slow fixtures, overuse TransactionTestCase, duplicate setup, or need refactoring for speed without losing coverage.

Create lightweight, living game design documents for AI-built games. Use when writing a game design brief, system spec, feature contract, content schema, implementation handoff, decision log, or when a coding agent needs durable project memory.

Design recurring B2B buyer-presence systems that keep a company remembered until pain becomes urgent, using time-based visibility cadence instead of unreliable intent signals or linear funnel assumptions. Use when buyers know the company but deals stall, follow-up is inconsistent, the team waits for triggers, expands markets too early, or wants a 4-6 week account visibility rhythm.

Apply the Bullseye framework from Traction to brainstorm, rank, test, and focus startup traction channels. Use when choosing growth channels, overcoming channel bias, prioritizing marketing experiments, or deciding which acquisition channel deserves focused effort.

Use when the user is unsure which LVTD skill fits their problem, asks what skill to use, describes a cross-domain workflow, or needs help choosing between Django, Rust, SEO, B2B sales, writing, product, library, or template skills.

Make a product, landing page, pricing page, launch page, free tool, or social preview easier to understand, buy, remember, and share using Marc Lou-inspired viral product patterns.

Audit and rewrite B2B sales messaging so the right buyers quickly understand the painful problem, concrete outcome, and mechanism behind the offer. Use when buyers see the company but do not remember it, cannot explain what it does, do not connect it to a trigger, or messaging sounds clever, vague, over-complex, generic, or too simplified for the buyer's world.

Plan seed marketing for useful nonfiction books so the first 500-1000 target readers can start word of mouth. Use when choosing launch channels, planning a podcast or digital book tour, Amazon PPC, event giveaways, bulk sales, writing in public, content schedules, or email capture for a practical book.

Design safe Django and PostgreSQL indexes from measured query plans, including B-tree, composite, covering, partial, expression, GIN/JSONB, BRIN, and concurrent migration patterns. Use when a Django query plan suggests missing or mismatched indexes, a production table needs an index without write downtime, or existing indexes need review.

Turn a game idea into a focused design problem, risk-first prototype plan, and iteration loop. Use when starting a game, choosing what to build first, scoping an MVP, defining design questions, planning prototypes, or deciding whether an idea is ready for production.

Plan beta reading rounds for practical nonfiction and turn reader comments, abandonment, confusion, skepticism, and negative feedback into manuscript revisions. Use when recruiting beta readers, preparing reader instructions, synthesizing feedback, deciding whether a book is ready, or improving a draft from real reader data.

Run broken link building and link equity salvage workflows by finding relevant resource pages, checking outbound link status, verifying dead URLs, qualifying dead backlinks, preparing replacement outreach, and mapping old owned URLs to redirects. Use when finding broken link prospects, replacing dead resources, recovering lost backlinks, or auditing old URLs after migrations and redesigns.

Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies. Use when tuning combat, loot, upgrades, scoring, level curves, AI difficulty, risk-reward choices, or any system where numbers shape player decisions.

Design and review game spatial query code for raycasts, picking, collision predicates, containment tests, orientation tests, and point/line/plane distances. Use when implementing or debugging ray-triangle hits, point-in-triangle checks, barycentric constraints, signed distance tests, or geometry predicates.

Plan, qualify, pitch, and track guest post placements that build links and expertise through audience-specific, citation-justified, editorially placeable off-site content. Use when checking guest post viability, making sales pages citable, creating guest post pitch titles, assessing publisher quality, reviewing guest post outreach, or tracking placements.

Design and review Bevy game state flow with plugins, AppState enums, OnEnter and OnExit setup, state-scoped cleanup, menus, pause screens, transitions, and run conditions. Use when adding reusable Bevy game state management, debugging duplicated entities after transitions, or separating menu, loading, playing, paused, and game-over logic.

Diagnose technical SEO issues using discovery, crawling, indexing, ranking, Google Search Console, internal links, crawl budget, canonicals, duplicate content, redirects, and migration risk. Use when traffic drops, pages are not indexed, Search Console shows errors, canonicals differ, migrations are planned, or a technical SEO audit is needed.

Plan PR-oriented traction experiments from Traction, including targeting blogs, publicity, and unconventional PR. Use when pitching bloggers or reporters, designing publicity stunts, earning launch coverage, or validating PR as a startup growth channel.

Plan SEO and content marketing traction experiments from Traction. Use when creating organic growth tests, SEO page strategies, content calendars, blog experiments, link-building tests, or deciding whether content can become a core acquisition channel.

Build B2B reach systems that make a defined market aware of the company through named accounts, real buyers, controlled delivery channels, and first-touch saturation. Use when the right market may not know the company exists, outbound gets little signal, brand awareness is vague, the target market is too broad, or the team needs a concrete account list and reach plan.

Engineer B2B buyer trust by reducing perceived risk, stacking relevant proof, simplifying next steps, and designing sales calls to confirm confidence rather than persuade from scratch. Use when qualified buyers take calls, request proposals, start trials, or show interest but then stall, ghost, choose safer incumbents, or hesitate because proof, certainty, process, or risk reversal is weak.

Diagnose and improve slow Django database-backed endpoints with evidence-first profiling, query-plan review, index selection, ORM loading fixes, batching, database-side computation, materialized views, and pagination choices. Use when a Django view, API, job, report, queryset, or database query is slow and the right optimization path is not obvious.

Profile and measure slow Django test suites with Django's runner, pytest-django, shell timing, py-spy, cProfile, pytest durations, and profiler visualizations. Use when a Django project has slow tests, unclear test-runtime bottlenecks, CI timing problems, startup overhead, database setup overhead, or a request to find the slowest tests before optimizing.

Design, inspect, or repair game mechanics, core loops, rules, goals, actions, state, chance, secrets, skills, and emergent dynamics. Use when building gameplay systems, combat, puzzles, progression, simulations, board/card mechanics, or any feature where rules create player behavior.

Use when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test isolation, external HTTP mocks, or CI-ready cargo verification for Actix, Axum, Warp, Rocket, or similar Rust web frameworks.

Use when adding, changing, testing, or reviewing security-sensitive Rust web service behavior, especially login flows, password hashing, credential checks, session cookies, flash messages, admin route protection, auth middleware, user enumeration defenses, or moving CPU-heavy password work off async executors.

Design and review Rust trait APIs, generic bounds, dispatch models, and conversion contracts for clear public interfaces. Use when designing, refactoring, or reviewing traits, generics, trait objects, associated types, impl Trait, From/TryFrom, AsRef, Borrow, or crate APIs.

Design cheap, measurable traction tests from Traction for startup growth channels. Use when planning marketing experiments, middle-ring tests, A/B tests, acquisition test spreadsheets, channel validation, or growth experiment success criteria.

Find the Django ORM code and request path responsible for slow SQL by using APM traces, slow query logs, Django Debug Toolbar, query logging, and local reproduction. Use when a Django database performance issue is suspected but the exact queryset, view, serializer, template, or job causing it is not yet proven.

Plan, run, and interpret game playtests. Use when validating prototypes, onboarding, difficulty, mechanics, UI clarity, retention, or fun; when writing playtest scripts, surveys, observation plans, or telemetry requirements.

Design and debug game transform systems, coordinate spaces, local/world/view/projection matrices, homogeneous coordinates, camera constraints, and inverse transforms. Use when implementing object transforms, camera math, parent-child transforms, projection/unprojection, or coordinate-space conversions.

Design sustainable link-building campaigns that connect business goals, linkable assets, publisher ecosystems, metrics, resources, and campaign templates. Use when planning a link-building campaign, choosing tactics, defining link-building KPIs, mapping links to business outcomes, or turning SEO authority goals into an executable campaign brief.

Audit and revise practical nonfiction drafts for reader experience, value pacing, front-loaded insight, value-per-page, boredom, and beta-readiness. Use when editing, restructuring, shortening, or reviewing a book, guide, manual, course-like manuscript, or long-form educational draft so readers receive useful value quickly and keep reading.

Design and review Rust async code around task ownership, suspension points, cancellation, blocking work, and runtime boundaries. Use when writing, refactoring, or reviewing futures, async functions, Tokio tasks, spawn, JoinHandle, Send futures, async traits, cancellation, or mutexes across await points.

Build and review bracket-lib style Rust 2D game loops, state structs, game modes, input handling, rendering calls, and restart flow. Use when creating a small Rust game with bracket-lib, porting a tutorial loop, or debugging tick/update/render state behavior.

Use when modeling, validating, refactoring, or reviewing Rust service domain boundaries, especially when replacing primitive String fields with newtypes, parse-don't-validate constructors, private invariants, TryFrom/FromStr parsers, request DTO boundaries, or property tests.

Design and review Rust FFI boundaries that keep raw declarations isolated behind safe ownership, lifetime, error, and cleanup wrappers. Use when writing, refactoring, or reviewing unsafe extern blocks, C ABI wrappers, repr(C) types, CString, CStr, raw handles, Drop cleanup, bindgen, cbindgen, or panic-safe foreign boundaries.

Isolate and review unsafe Rust behind small, documented, testable boundaries with explicit invariants. Use when writing, refactoring, or reviewing unsafe code, raw pointers, unsafe functions, unsafe traits, MaybeUninit, pointer aliasing, panic safety, Miri checks, or safe abstractions over unsafe internals.

Set traction goals and identify the Critical Path from Traction so teams focus only on milestones needed for growth. Use when a startup has too many priorities, needs growth goals, is debating product versus marketing work, or wants to decide what not to do.

Optimize useful nonfiction book sales after the book is already working, including Amazon or retailer funnels, cover thumbnail clarity, store descriptions, authentic reviews, extra formats, pricing, upsells, piracy hooks, and fan engagement. Use when improving a book product page, purchase funnel, format strategy, pricing, direct sales, or post-launch growth.

Turn customer conversation notes, interview transcripts, call summaries, CRM snippets, or research notes into shared team learning and next questions. Use when synthesizing raw customer notes, avoiding founder interpretation bottlenecks, extracting quotes and signals, updating beliefs, or deciding what to ask next.

Mock Django test boundaries safely with override_settings, pytest settings, autospecced unittest.mock objects, output/input capture, requests-mock, VCR.py, outbound HTTP blocking, and time-freezing tools. Use when tests need to replace settings, HTTP calls, time, command output, stdin, or external services without broad fragile MagicMock patches.

Improve slow Django test suites through measured profiling, safe test settings, database and migration tuning, parallel execution, test-data cleanup, and CI workflow changes. Use when Django or pytest-django tests are slow, CI test jobs take too long, database setup dominates runtime, or a user asks for a prioritized speedup plan rather than isolated test fixes.

Design or audit game controls, HUD, menus, feedback, input mapping, transparency, juiciness, channels, modes, and metaphors. Use when implementing UI, controls, camera, tutorials, status displays, accessibility feedback, or when players are confused about what happened.

Plan, audit, and prioritize linkable assets that publishers, curators, experts, and community owners have a real reason to cite. Use when creating link-worthy content ideas, auditing existing assets, turning market pains into assets, analyzing competitor linkable content, or deciding what to build before link prospecting and outreach.

Use when preparing, containerizing, configuring, testing, or reviewing Rust services for deployment, especially Docker multi-stage builds, runtime configuration, environment overrides, secrets, health checks, SQLx offline builds, release profiles, image-size reduction, or production startup validation.

Narrow broad customer categories into specific, reachable who-where segments for customer discovery, positioning, traction tests, sales outreach, or SEO personas. Use when feedback is inconsistent, the market is too broad, personas are vague, users request too many different features, or the team does not know where to find target customers.

Keep technical nonfiction durable by separating timeless concepts, decision frameworks, and reader outcomes from fast-changing tool walkthroughs, UI steps, versions, vendor details, and companion resources. Use when scoping, outlining, revising, or updating technical books, self-hosting guides, software manuals, DevOps books, or other technical manuscripts that risk becoming outdated.

Create product-led SEO strategies that turn product value, user intent, page architecture, taxonomy, and scalable user experiences into organic growth. Use when a user asks for SEO strategy, organic growth planning, content/product SEO, programmatic SEO direction, search moat creation, or wants to avoid keyword-list SEO.

Build and review Bevy game asset loading pipelines with typed asset catalogs, path validation, loading states, handle ownership, sprite sheets, audio, and runtime resource checks. Use when organizing Bevy assets, replacing hard-coded paths, adding loading screens, diagnosing missing handles, or packaging Rust game resources.

Use when adding, changing, debugging, or reviewing Rust service error handling and observability, especially when separating domain errors from HTTP responses, adding thiserror/anyhow, implementing ResponseError or IntoResponse, adding tracing spans, redacting secrets, or diagnosing async failures.

Finish and package small Rust games with MVP lock, playability checks, resource packaging, release builds, smoke tests, and disciplined post-MVP polish. Use when preparing a Rust game prototype for sharing, packaging bracket-lib assets, or deciding what finishing work belongs before release.