wdm0006
- 61 skills
- 0 followers
- 6 hours ago last updated
- ▌ Local Dev · wdm0006Stand up a working local dev environment for wdm0006/elote — uv + Python 3.11 venv, full test suite, lint, typecheck, and a primary-flow smoke test
- ▌ Weekly Review · wdm0006Generates a weekly summary of your idea.log activity — new ideas captured, progress made, ideas completed or abandoned — with suggestions for what to focus on next. Use at the start or end of each week.
- ▌ Idea Interview · wdm0006Conducts an interactive conversation to flesh out a vague or half-formed idea into something specific and actionable. Asks clarifying questions, suggests tags and first steps, and updates the idea in idea.log. Use when you have a rough concept that needs development.
- ▌ Backlog Grooming · wdm0006Reviews all pending ideas in idea.log, cleans up stale or duplicate entries, improves descriptions, suggests tags, and helps prioritize what to work on next. Use when your idea backlog feels cluttered or you want to start a focused work session.
- ▌ Stale Ideas Audit · wdm0006Finds ideas that have been sitting untouched in your backlog and helps you decide what to do with each one — revive it, refine it, or abandon it. Use when your backlog has accumulated cruft over time.
- ▌ Autonomous Builder · wdm0006Picks an idea from your idea.log backlog and autonomously starts building it — scaffolding a project, writing initial code, setting up the repo. Use when you want to turn an idea into a real project without doing the setup yourself.
- ▌ Idea Decomposition · wdm0006Breaks a large or complex idea into smaller, actionable sub-ideas, each with their own first steps and tags. Creates the sub-ideas in idea.log and links them back to the parent. Use when an idea feels too big to start.
- ▌ Scanning Inbox For Evergreen · wdm0006Scans Gmail for actionable items and maps them to Evergreen CRM contacts — unanswered questions, promised deliverables, introduction requests, and follow-ups needed. Use when triaging your inbox, catching missed commitments, or syncing email activity to your CRM. Requires Gmail connected in Claude.
- ▌ Evergreen Life Event Tracker · wdm0006Tracks and acts on life events and milestones for Evergreen CRM contacts — birthdays, work anniversaries, job changes, promotions, and personal milestones. Use when you want to stay on top of important dates and send timely, thoughtful messages.
- ▌ Evergreen News Alerts · wdm0006Monitors news and web mentions for Evergreen CRM contacts and their companies — funding rounds, product launches, press coverage, job changes. Use to surface timely conversation starters and stay informed about your network's activities.
- ▌ Evergreen Meeting Prep · wdm0006Generates a pre-meeting briefing from Evergreen CRM — contact profiles, interaction history, shared connections, open actions, and suggested talking points. Use before any meeting, call, or coffee chat to refresh your memory and show up prepared.
- ▌ Re Engaging Evergreen Contacts · wdm0006Identifies dormant contacts in Evergreen CRM and drafts natural re-engagement messages. Use when you want to reconnect with people you haven't spoken to in months, revive stale relationships, or systematically re-engage your extended network.
- ▌ Evergreen Weekly Report · wdm0006Generates a weekly relationship management digest from Evergreen CRM — interactions logged, follow-ups completed vs missed, network growth, and a spotlight contact. Use for weekly reviews, accountability, or planning the week ahead.
- ▌ Evergreen Context Recall · wdm0006Generates a narrative summary of everything known about a contact in Evergreen CRM — how you met, what you've discussed, mutual connections, and pending threads. Use when you need to quickly refresh your memory before reaching out, replying, or meeting someone.
- ▌ Capturing Contacts In Evergreen · wdm0006Parses unstructured text (email signatures, business cards, LinkedIn profiles, meeting notes) into structured Evergreen CRM contacts. Use when adding new contacts from raw text, importing contacts from emails or messages, or batch-creating contacts from event notes.
- ▌ Drafting Evergreen Follow Ups · wdm0006Drafts personalized follow-up emails and messages based on Evergreen CRM contact history, past interactions, and pending actions. Use when you need to write a follow-up email, thank-you note, check-in message, or any outreach to an existing contact.
- ▌ Evergreen Event Follow Up · wdm0006Batch-processes contacts from a conference, dinner, or networking event into Evergreen CRM — creates records, tags them by event, and drafts personalized follow-up messages. Use after any event where you met multiple new people.
- ▌ Evergreen Network Analysis · wdm0006Analyzes your Evergreen CRM contact network to surface clusters, bridge contacts, top introducers, and introduction chains. Use when you want to understand your network structure, find connection opportunities, or identify key people in your network.
- ▌ Evergreen Stale Data Audit · wdm0006Audits Evergreen CRM for stale or incomplete contact data — outdated titles, missing fields, potential duplicates, and contacts that may have changed jobs. Use for periodic database hygiene, before a big outreach push, or when data quality feels off.
- ▌ Drafting Warm Introductions · wdm0006Drafts double-opt-in introduction emails connecting two Evergreen CRM contacts. Use when someone asks for an introduction, when you spot a mutually beneficial connection, or when facilitating networking between contacts.
- ▌ Enriching Evergreen Contacts · wdm0006Researches and enriches Evergreen CRM contacts with publicly available information — LinkedIn details, company info, recent news, and shared context. Use when a contact has sparse details, before an important meeting, or when batch-updating stale records.
- ▌ Processing Meeting Notes For Evergreen · wdm0006Processes raw meeting notes into structured Evergreen CRM records — logs interactions, creates action items, adds new contacts, and updates notes. Use after any meeting, call, or conversation to capture everything in your CRM without manual data entry.
- ▌ Evergreen Follow Up Reminders · wdm0006Generates a prioritized follow-up list from Evergreen CRM based on overdue actions, stale contacts, and interaction cadences. Use when planning your week, checking who needs attention, or building a daily outreach list.
- ▌ Evergreen Relationship Health · wdm0006Scores and surfaces relationship health across your Evergreen CRM contacts — identifies thriving relationships, ones at risk, and dormant connections needing attention. Use when you want a high-level view of your network health or need to prioritize relationship investment.
- ▌ Auto Logging Email Interactions · wdm0006Parses recent Gmail activity and logs interaction summaries to Evergreen CRM contacts — without storing full email bodies. Use when you want to sync email activity to your CRM, update interaction history, or keep Evergreen current with your communications. Requires Gmail connected in Claude.
- ▌ Building Swift Apps · wdm0006Builds, tests, and ships native Swift/SwiftUI apps for Apple platforms (macOS/iOS) reliably in CI and locally — unsigned CI builds, the hand-maintained pbxproj, SwiftPM-module vs app-target test boundaries, SourceKit false positives, gitignored base xcconfig, Keychain vs UserDefaults for secrets (OAuth state/PKCE), CloudKit/SwiftData constraints, and deterministic date/RNG handling. Use when wiring CI for an Xcode project, debugging "requires a provisioning profile" / "no testable scheme" / "cannot find type in scope", adding a Swift file to a target, wiring OAuth sign-in, or reviewing a Swift app.
- ▌ Building Go Projects · wdm0006Sets up and maintains Go projects with a CI gate that actually gates — module-path correctness, golangci-lint config that matches the installed major version, deterministic gofmt, a pinned toolchain, and meaningful test/lint jobs. Use when creating a Go module, wiring GitHub Actions for Go, debugging a golangci-lint or gofmt CI failure on an unrelated PR, or reviewing a Go CLI that shells out to git/gh.
- ▌ Building Rust Crates · wdm0006Sets up, tests, and publishes Rust crates — Cargo project layout, a fmt/clippy/test CI gate that actually gates, MSRV pinning, feature-flag hygiene, and crates.io publishing with cargo-release. Use when creating a Rust crate, wiring GitHub Actions for Rust, debugging a clippy or MSRV CI failure, or preparing a crates.io release.
- ▌ Building Scala Projects · wdm0006Sets up, tests, and publishes Scala projects — sbt build layout, scalafmt/scalafix as CI gates, Scala 2-vs-3 and cross-building, a test job that actually runs, and Maven Central publishing via sbt-ci-release. Use when creating an sbt project, wiring GitHub Actions for Scala, debugging a cross-build or scalafmt CI failure, or preparing a Sonatype/Maven Central release.
- ▌ Shipping Swift Apps · wdm0006Ships native Swift/SwiftUI apps to TestFlight and the App Store with fastlane and xcodebuild — one App Store Connect API key for both, fastlane lanes scoped to metadata/pricing/subscriptions, headless `xcodebuild archive` + `-exportArchive destination=upload`, build numbers read from App Store Connect instead of guessed, closed pre-release trains, `SKIP_INSTALL` for bundled helper apps, and per-destination archives for multiplatform targets. Use when setting up fastlane for an Xcode project, uploading a build to TestFlight from a script or CI, or debugging "Invalid Pre-Release Train", "expected one {} but found app-store-connect", "Unknown Distribution Error", or a duplicate-build-number rejection.
- ▌ Running Resumable Sync Jobs · wdm0006Design and review long-running batch or sync jobs that process many items against a remote API and persist checkpoint state — exit codes that report partial failure, checkpoints that are safe to resume, per-item tolerance vs. fatal abort, telling "zero" apart from "couldn't fetch", bounded retries, honest dry-runs, timezone-safe incremental cursors, and compensating reserved resources. Use when writing or reviewing a mirror/sync command, a nightly cron job, an importer, a paginated fetcher, or a background worker that consumes quota.
- ▌ Building Python Communities · wdm0006 bundleBuilds and manages open source Python library communities including CONTRIBUTING.md, CODE_OF_CONDUCT.md, issue/PR templates, contributor recognition, and GitHub automation. Use when setting up community infrastructure, improving contributor experience, or managing project governance.
- ▌ Packaging Python Libraries · wdm0006 bundlePackages and distributes Python libraries using modern pyproject.toml, build backends (setuptools, hatchling), PyPI publishing with trusted publishing, and wheel building. Use when packaging libraries for distribution, publishing to PyPI, or troubleshooting packaging issues.
- ▌ Wiring Application Config · wdm0006Load, merge, and validate layered application configuration (defaults plus a user YAML/TOML/JSON file or a stored settings object) so a mis-wired or misspelled key fails loudly instead of silently reverting to the default — sections the code reads that exist nowhere, sections that exist but nothing reads, unvalidated recursive merges, `bool`-passes-as-`int`, defaults aliased by a shallow merge, falsy-but-valid values killed by `or`/`||`, partial write-backs that are stickier than a missing file, and bootstrap ordering that swallows the loader's own warnings. Use when adding a config key, writing or reviewing a config loader/merge/schema, reading a setting in a new module, persisting user settings, wiring logging from config, or debugging a setting that "has no effect".
- ▌ Designing Python Apis · wdm0006 bundleDesigns intuitive Python library APIs following principles of simplicity, consistency, and discoverability. Handles public re-exports, API evolution, deprecation, breaking changes, and error handling. Use when designing or reviewing a library API, exposing a symbol from a package __init__, or managing API versioning and deprecations.
- ▌ Keeping Git Repos Clean · wdm0006Prevents, detects, and remediates files that should never be committed — secrets (.env, API tokens, hardcoded credentials) and dev artifacts (build output, scratch databases, editor/OS files). Covers .gitignore (and why it does not untrack), git rm --cached, auditing tracked files, history scrubbing, and credential rotation. Use when a repo has committed secrets or junk, when setting up a new repo's ignore rules, or when reviewing what a repo actually tracks.
- ▌ Building Python MCP Servers · wdm0006Builds robust Python MCP (Model Context Protocol) servers with FastMCP — tool design, error contracts, event-loop-safe blocking work, subprocess/CLI wrapping, single-file vs packaged distribution, global-state-free testing, and prompt-injection awareness. Use when writing an MCP server, exposing a tool or CLI to an LLM client, debugging tool registration/packaging, or testing MCP tools.
- ▌ Optimizing Python Performance · wdm0006 bundleOptimizes Python library performance through profiling (cProfile, PyInstrument), memory analysis (memray, tracemalloc), benchmarking (pytest-benchmark), and optimization strategies. Use when analyzing performance bottlenecks, finding memory leaks, or setting up performance regression testing.
- ▌ Improving Python Code Quality · wdm0006 bundleImproves Python library code quality through ruff linting, mypy type checking, Pythonic idioms, and refactoring. Use when reviewing code for quality issues, adding type hints, configuring static analysis tools, or refactoring Python library code.
- ▌ Building LLM Backed Features · wdm0006Builds application features on top of an LLM API in Python — prompt surfaces that drift apart, structured outputs, context budgeting, model/config wiring, filtered evaluator sets, keeping live-model calls out of default CI, evaluating stochastic output, and presenting model output truthfully. Use when adding an LLM call to an app, designing structured outputs or prompt templates, filtering audit rules, wiring model config, or testing/evaluating LLM-backed analysis.
- ▌ Documenting Python Libraries · wdm0006 bundleCreates comprehensive Python library documentation including Google-style docstrings, Sphinx setup, API references, tutorials, and ReadTheDocs configuration. Use when writing docstrings, setting up Sphinx documentation, or creating user guides for Python libraries.
- ▌ Setting Up Python Libraries · wdm0006 bundleSets up professional Python library projects with modern tooling (pyproject.toml, uv, ruff, pytest, pre-commit, GitHub Actions). Use when creating new Python libraries, modernizing existing projects to pyproject.toml, configuring linting/testing/CI, or setting up Makefiles and pre-commit hooks.
- ▌ Writing Defect Reports · wdm0006Establish a finding before you publish it, and correct it after — headlines that overstate what actually reproduces at the layer a user sees, reporting code that no entry point can reach or that is already dead, filing a caveat the project's own records already answered, re-verifying your prior notes against the tree instead of against the note, choosing the narrowest injection point that reproduces a failure without breaking the run first, capturing probe output a harness swallows, and withdrawing a published claim in the thread where you published it. Use when filing an issue, writing the body of a PR or code review that asserts a defect, triaging someone else's report, or deciding whether a suspicious observation is reportable at all.
- ▌ Running Github Actions Efficiently · wdm0006Cut GitHub Actions minutes and wall-clock time without losing coverage — the OS billing multiplier (macOS 10x / Windows 2x / Linux 1x), trigger hygiene that stops push+pull_request double-firing, concurrency that cancels superseded runs, dependency caching keyed on lockfiles, matrix discipline, and auditing scheduled crons that bill 24/7. Use when CI is burning included minutes, when runs feel slow, when setting up a new repo's workflows, or when reviewing an existing workflow for waste.
- ▌ Reviewing Python Libraries · wdm0006 bundleComprehensively reviews Python libraries for quality across project structure, packaging, code quality, testing, security, documentation, API design, and CI/CD. Provides actionable feedback and improvement recommendations. Use when evaluating library health, preparing for major releases, or auditing dependencies.
- ▌ Auditing Python Security · wdm0006 bundleAudits Python libraries for security vulnerabilities using Bandit, pip-audit, Semgrep, and detect-secrets. Identifies SQL injection, command injection, hardcoded credentials, secrets exposed through tracebacks, weak cryptography, and insecure deserialization. Use when reviewing library security, setting up security scanning in CI, or implementing secure coding patterns.
- ▌ Shipping Build Artifacts · wdm0006Make the build step a real gate on what you actually distribute — build scripts that warn and exit 0 on a missing input, size checks with only an upper bound, hand-maintained file lists that drift from the entrypoints they must cover, committed bundles that go stale when only the source changes, GNU-only shell in release scripts that aborts on the other OS, and verification that runs against the source tree instead of the artifact. Use when writing or reviewing a build/package script, a `dist/` copy step, a release workflow that uploads a zip or installer, or a committed compiled asset.
- ▌ Reporting Derived Metrics · wdm0006Compute statistics, scores, and flags from samples that may be too small to support them — undefined dispersion returned as 0.0 and tripping a minimum threshold, sentinel choice (None vs 0 vs NaN), threshold blocks gated on "was this measured", reports that narrate findings from absent data, nullability as a public API change, `is None` vs truthiness, and broad excepts that turn a metric bug into a normal-shaped result. Use when writing or reviewing a scoring/analysis pipeline, a z-score or outlier check, a quality or anomaly flag, a metrics rollup, or any function that reduces a list of observations to one number a threshold reads.
- ▌ Building Python Clis · wdm0006 bundleBuilds command-line interfaces for Python libraries using Click or Typer. Includes command groups, argument handling, progress bars, shell completion, and CLI testing with CliRunner. Use when adding CLI functionality to a library or building standalone command-line tools.
- ▌ Testing Python Libraries · wdm0006 bundleDesigns and implements pytest test suites for Python libraries with fixtures, parametrization, mocking, Hypothesis property-based testing, and CI configuration. Use when creating tests, improving coverage, setting up testing infrastructure, or implementing property-based testing.
- ▌ Deferring Heavy Dependencies · wdm0006Keep expensive resources — ML models, spellcheck dictionaries, embedded databases, large third-party imports — off code paths that never use them. Covers constructor work paid by every caller, one-size factories that load the heaviest member for the cheapest request, load-and-unload-per-call masquerading as a cache, measuring per-call cost in a fresh process, telling a one-time import from a repeated model load, and the test fallout (patches that only now take effect, autouse fixtures that hide the dependency). Use when a trivially cheap operation takes hundreds of milliseconds, when adding a heavy dependency to a shared constructor or factory, or when reviewing a class whose `__init__` builds something most callers never touch.
- ▌ Normalizing Text For Measurement · wdm0006Strip, parse, and segment a document before something else measures it — normalizers that fuse two blocks into one word because a close-token emits no separator, the two metric classes failing on different residue — character-based ones (reading time, token budgets, size limits) inflated by leftover syntax, word-based ones (word count, readability) corrupted by boundaries the strip never inserted — sibling consumers that skip the normalizer entirely, parser presets whose rule set silently reclassifies a construct, sections grouped by a non-unique heading key that collapse and double-count into an ancestor, and deliberate lossiness that the next reader mistakes for a bug. Use when writing or reviewing a markdown/HTML stripper, a plain-text extractor, a section or paragraph splitter, a reading-time/word-count/readability/token-count function, a dedup key or checksum built from prose, or a search-index preprocessing step.
- ▌ Managing Python Releases · wdm0006 bundleManages Python library releases including semantic versioning, changelog maintenance (Keep a Changelog format), release automation with GitHub Actions, and deprecation workflows. Use when planning releases, writing changelogs, automating release pipelines, or communicating breaking changes.
- ▌ Concurrent Branches · wdm0006Resolve conflicts and merges when several branches are open against one repo at the same time — the hotspot files every change must touch (registry manifests, a single version field, shared tool config, one aggregated test module, tracked build output), union-vs-recompute-vs-rebuild as three different correct resolutions, generated artifacts that must never be merged, non-deterministic serialization that makes every branch conflict, renumbered identifiers that git cannot show you, and why a clean auto-merge is not a passing test. Use when rebasing or merging a long-lived branch, resolving conflict markers, reviewing a merge commit, deciding what a repo should commit vs generate, or setting up a repo that will take parallel contributions.
- ▌ Building Python Web Apps · wdm0006 bundleProvides an opinionated reference architecture for production Python web apps — FastAPI + async SQLAlchemy + Postgres, pydantic-settings config, Stripe billing, server-rendered Jinja or a decoupled SPA, deployed as a single Docker image on a managed platform via Terraform. Use when starting a new SaaS/web app, choosing a stack, structuring routers/services/models, wiring Stripe webhooks, protecting FastAPI docs or OpenAPI routes, setting up config/secrets, or deciding how to deploy.
- ▌ Shipping Across Surfaces · wdm0006Land a change everywhere the same fact is stated — enumerating the full surface inventory (landing copy, docs, machine-readable summaries, changelog badges repeated across every page, sitemap, README, descriptions embedded in code, and untyped frontend consumers of typed responses), generating a surface instead of restating it, drift tests where you cannot generate, never hand-maintaining a copy of a surface another codebase owns, shipping a paired PR when you change a format a different codebase decodes, and keeping overloaded product words apart. Use when adding or renaming a user-facing feature, editing product/marketing copy or docs, renaming a serialized response field, changing a serialization or share-link format, wiring one repo's output into another's checks, or reviewing a PR that touched only one place a fact appears.
- ▌ Guarding Destructive Operations · wdm0006Add and review preconditions on operations that delete, overwrite, rewrite history, or resolve a caller-supplied name to a filesystem path — refusing instead of warning, placing the guard ahead of the first mutation, structural classification rather than string-prefix matching, name validation plus resolved-path containment as two independent checks, why a guard on the destructive path is invisible to the dry-run, and mutation-testing each half separately. Use when writing or reviewing a `--rebuild`/`--reset`/`--purge` command, a bulk delete, a history rewrite, an `rm -rf`-shaped step, or any code that turns an argument into a file path.
- ▌ Reproducing CI Locally · wdm0006Run the CI gate on your machine so it agrees with the runner — deriving the exact command, paths, markers, and env from the workflow file instead of the Makefile, unblocking gate steps that short-circuit and hide the next failure, pinning the linter version CI resolves, building the interpreter/toolchain environment the runner builds, and confirming the run is green instead of explaining a red job away. Use when a check passes locally but fails in CI (or the reverse), when a lint/format job goes red on an untouched file, when setting up a local dev loop for an unfamiliar repo, or before pushing a branch you expect to merge.
- ▌ Building Browser Extensions · wdm0006Builds and tests Manifest V3 browser extensions — service-worker message channels that survive teardown, chrome.storage read-modify-write safety, settings validation in the popup, and a Jest chrome mock that can actually fail. Use when writing or reviewing a background service worker, a popup that reads/writes chrome.storage, an extension's Jest suite, or debugging an extension whose UI silently stops responding.
- ▌ Rendering Untrusted Content · wdm0006Renders stored, authored, or imported content into HTML without shipping XSS — auditing every autoescape bypass (|safe, Markup, innerHTML), sanitizing Markdown output with an allowlist, escaping on both the server and the DOM, and writing sanitization tests that assert on the right copy of the string. Use when adding a Markdown or rich-text filter, rendering user/admin-authored content, reviewing a template that marks HTML trusted, building a client that injects values into innerHTML, or fixing an XSS report.
- ▌ Verifying External Behavior · wdm0006Confirms what a third-party library, remote API, build backend, or scraped document actually does before writing code that depends on it — throwaway probes that run in seconds, permissive clients that forward wrong arguments instead of rejecting them, per-endpoint docs that don't generalize, response shapes that make a "fast path" always-false, fakes that encode your assumption rather than the service's behavior, and dry-runs that skip the step that fails. Use when integrating a new dependency or endpoint, writing a tolerated-status or error branch, choosing a client argument name, testing against a fake, or reviewing code that asserts an upstream contract.