livelybug
- 254 skills
- 0 followers
- 2 weeks ago last updated
- ▌ Writing Shape · livelybugWriting, exploit — shape raw material into an article, paragraph by paragraph.
- ▌ Trellis Channel · livelybug bundleUse Trellis channel for live multi-agent collaboration, spawned workers, cross-agent review, progress inspection, forum channels, and channel log debugging.
- ▌ Ce Plan · livelybug bundleCreate structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.
- ▌ Ce Work · livelybug bundleExecute a plan or concrete work prompt end-to-end. Use when implementing from docs/plans, a spec path, or a clear build request; use ce-debug for open-ended bugs.
- ▌ Hackernews Frontpage · livelybugScrape the Hacker News front page (titles, points, comment counts).
- ▌ Trellis Continue · livelybugResume work on the current task. Loads the workflow Phase Index, figures out which phase/step to pick up at, then pulls the step-level detail via get_context.py --mode phase. Use when coming back to an in-progress task and you need to know what to do next.
- ▌ Ce Debug · livelybug bundleDiagnosis loop for bugs and failing behavior. Use for errors, stack traces, regressions, failed tests, issue-tracker bugs, stuck investigations after failed fixes, or asks to debug/fix a bug.
- ▌ Ce Proof · livelybugPublish, read, comment on, or edit markdown in Proof. Use for Proof links, sharing specs/plans/drafts, or publish handoffs from planning workflows; avoid proofread, math, evidence, or proof-of-concept meanings.
- ▌
- ▌ Codebase Design · livelybug bundleShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
- ▌ Diagnosing Bugs · livelybug bundleDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
- ▌ Domain Modeling · livelybug bundleBuild and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
- ▌ Ce Commit · livelybugCreate a git commit with a clear, value-communication message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate, value-communicating message.
- ▌ Ce Ideate · livelybug bundleGenerate and evaluate grounded ideas. Use when the user asks for ideas, improvements, surprising options, or AI-generated directions before choosing one to develop; use ce-brainstorm to refine the user's own idea.
- ▌ Ce Polish · livelybug bundleStart the dev server, inspect the feature in browser, and iterate on polish.
- ▌ Gstack Openclaw Retro · livelybugWeekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas. Use when asked for weekly retro, what shipped this week, or engineering retrospective.
- ▌ Decision Mapping · livelybugTurn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
- ▌ Trellis Before Dev · livelybugDiscovers and injects project-specific coding guidelines from .trellis/spec/ before implementation begins. Reads spec indexes, pre-development checklists, and shared thinking guides for the target package. Use when starting a new coding task, before writing any code, switching to a different package, or needing to refresh project conventions and standards.
- ▌ Trellis Brainstorm · livelybugGuides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex task.
- ▌ Trellis Break Loop · livelybugDeep bug analysis to break the fix-forget-repeat cycle. Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs. Use after fixing a bug to prevent the same class of bugs.
- ▌ Spec Driven Development · livelybugCreates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
- ▌
- ▌
- ▌ Trellis Finish Work · livelybugWrap up the current session: verify quality gate passed, remind user to commit, archive completed tasks, and record session progress to the developer journal. Use when done coding and ready to end the session.
- ▌ Trellis Update Spec · livelybugCaptures executable contracts and coding conventions into .trellis/spec/ documents. Use when learning something valuable from debugging, implementing, or discussion that should be preserved for future sessions.
- ▌ Ce Compound · livelybug bundleDocument a recently solved problem or durable project vocabulary in docs/solutions/ or CONCEPTS.md. Use when capturing a learning after work.
- ▌ Ce Optimize · livelybug bundleRun metric-driven optimization loops. Use when improving measurable outcomes such as search relevance, clustering quality, build performance, prompt quality, or scored behavior through experiments.
- ▌ Ce Strategy · livelybug bundleCreate or update STRATEGY.md. Use when starting a product, changing direction or roadmap, or when ce-ideate, ce-brainstorm, or ce-plan need upstream product grounding.
- ▌ Ce Worktree · livelybugSet up isolated git worktrees. Use when starting isolated work, or when ce-work/ce-code-review offers a worktree option; detect existing isolation first.
- ▌ Literature Review · livelybugSystematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
- ▌ Ce Brainstorm · livelybug bundleExplore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning.
- ▌ Ce Doc Review · livelybug bundleReview requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.
- ▌
- ▌ Request Refactor Plan · livelybugCreate a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
- ▌ Trellis Spec Bootstrap · livelybug bundleBootstrap project-specific Trellis coding specs with a platform-neutral single-agent workflow. Use when creating or refreshing .trellis/spec guidelines, analyzing a codebase with GitNexus, ABCoder, or source inspection, decomposing package/layer spec work, and writing real codebase-backed spec docs without placeholder text.
- ▌ Git Workflow And Versioning · livelybugStructures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.
- ▌ Planning And Task Breakdown · livelybugBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
- ▌ Scholar Evaluation · livelybugStructured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
- ▌ Ce Code Review · livelybug bundleStructured code review for bugs, regressions, tests, and standards. Use before PRs or when asked for review; interactive mode can fix locally, while mode:agent reports only for pipeline callers.
- ▌ Gstack Openclaw Ceo Review · livelybugUse when asked to review a plan, challenge a proposal, run a CEO review, poke holes in an approach, think bigger about scope, or decide whether to expand or reduce the plan.
- ▌ Writing Great Skills · livelybug bundleReference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
- ▌ Trellis Session Insight · livelybug bundleReach into past AI conversation history through the `trellis mem` CLI. Use whenever the user asks 'how did we solve X last time', 'have we discussed this before', 'what was the decision on X', 'remind me what we did in this task', '上次怎么解的', '之前讨论过吗', '想起一段对话', or when starting a brainstorm that overlaps prior work, debugging a familiar bug, continuing a task across sessions, or doing a finish-work review. Returns raw past dialogue; decide for the moment whether to update spec, append to task notes, quote inline in the answer, or just internalize.
- ▌ Ce Dogfood Beta · livelybug bundle[BETA] Hands-off end-to-end branch dogfood pass with browser testing, auto-fixes, regression tests, and fix commits.
- ▌
- ▌ Gstack Openclaw Investigate · livelybugUse when asked to debug, fix a bug, investigate an error, or do root cause analysis, and when users report errors, stack traces, unexpected behavior, or say something stopped working.
- ▌ Ce Product Pulse · livelybug bundleGenerate time-windowed product pulse reports from configured signals.
- ▌ Ce Simplify Code · livelybugSimplify recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use for tidy/refactor passes; use ce-debug for bugs.
- ▌ Gstack Openclaw Office Hours · livelybugUse when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.
- ▌ First Principles Thinking · livelybug bundleSystematic first principles thinking for any problem domain. Use when the user says "analyze from first principles", "第一性原理", "从根本分析", "从零开始思考", "think from scratch", "question this design", "is this the right approach", "challenge assumptions", "挑战假设", "为什么要这样做", "有没有更好的方案", "why are we doing it this way", or needs to evaluate decisions, designs, or strategies without relying on analogies, conventions, or "best practices". Also triggers on "这个设计合理吗", "从本质上看", "回到基本面", "what's really true here", "what are we assuming", or any request to decompose a problem to its fundamentals.
- ▌ Ce Commit Push Pr · livelybug bundleCommit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
- ▌ Setup Matt Pocock Skills · livelybug bundleConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
- ▌ Resolving Merge Conflicts · livelybugUse when you need to resolve an in-progress git merge/rebase conflict.
- ▌ Ce Compound Refresh · livelybug bundleRefresh docs/solutions learnings against the current codebase. Use when auditing stale, overlapping, superseded, or drifted learnings; avoid general refactor, debugging, or code review unless docs/solutions is explicit.
- ▌ Ce Resolve Pr Feedback · livelybug bundleResolve PR review feedback. Use when addressing review comments, resolving review threads, or fixing code-review feedback.
- ▌ Improve Codebase Architecture · livelybug bundleScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
- ▌ Ce Riffrec Feedback Analysis · livelybug bundleAnalyze Riffrec feedback captures from bundles or standalone recordings. Always load for `riffrec-*.zip`, `session.json` + `events.json` + `recording.webm` + `voice.webm` bundles, `.mp4`/`.mov`/`.webm` videos, `.m4a`/`.mp3`/`.wav` audio, or capture/share requests.
- ▌ Codex · livelybug bundleProvides three modes — code review, adversarial challenge, and consult — for obtaining a second opinion on code.
- ▌ Crosspost · livelybugMulti-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.
- ▌ Ecc Guide · livelybugGuide users through ECC's current agents, skills, commands, hooks, rules, install profiles, and project onboarding by reading the live repository surface before answering.
- ▌ Email Ops · livelybugEvidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC. Use when the user wants to organize email, draft or send through the real mail surface, or prove what landed in Sent.
- ▌ Gateguard · livelybugFact-forcing gate that blocks Edit/Write/Bash (including MultiEdit) and demands concrete investigation (importers, data schemas, user instruction) before allowing the action. Measurably improves output quality by +2.25 points vs ungated agents.
- ▌ Motion UI · livelybugProduction-ready UI motion system for React/Next.js. Use when implementing animations, transitions, or motion patterns.
- ▌ Repo Scan · livelybugCross-stack source code asset audit — classifies every file, detects embedded third-party libraries, and delivers actionable four-level verdicts per module with interactive HTML reports.
- ▌ UI To Vue · livelybugUse when the user has UI screenshots or design exports that need batch conversion into Vue 3 components, especially with Vant, Element Plus, or Ant Design Vue.
- ▌ Design Review · livelybug bundleDesigner's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. (gstack)
- ▌ Agent Eval · livelybugHead-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics
- ▌ Agent Sort · livelybugBuild an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
- ▌ Agentic Os · livelybugBuild persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases.
- ▌ API Design · livelybugREST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
- ▌ Browser QA · livelybugUse this skill to automate visual testing and UI interaction verification using browser automation after deploying features.
- ▌ Django Tdd · livelybugDjango testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.
- ▌ Exa Search · livelybugNeural search via Exa MCP for web, code, and company research. Use when the user needs web search, code examples, company intel, people lookup, or AI-powered deep research with Exa's neural search engine.
- ▌ Github Ops · livelybugGitHub repository operations, automation, and management. Issue triage, PR management, CI/CD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task beyond simple git commands.
- ▌ Design Shotgun · livelybugDesign shotgun: generate multiple AI design variants, open a comparison board, collect structured feedback, and iterate. (gstack)
- ▌
- ▌
- ▌ Brand Voice · livelybug bundleBuild a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.
- ▌ Bun Runtime · livelybugBun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.
- ▌ Cpp Testing · livelybugUse only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
- ▌ E2e Testing · livelybugPlaywright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.
- ▌ Laravel Tdd · livelybugLaravel testing strategies with PHPUnit, Pest, model factories, HTTP tests, Sanctum authentication testing, mocking, and coverage.
- ▌ Manim Video · livelybug bundleBuild reusable Manim explainers for technical concepts, graphs, system diagrams, and product walkthroughs, then hand off to the wider ECC video stack if needed. Use when the user wants a clean animated explainer rather than a generic talking-head script.
- ▌ Quarkus Tdd · livelybugTest-driven development for Quarkus 3.x LTS using JUnit 5, Mockito, REST Assured, Camel testing, and JaCoCo. Use when adding features, fixing bugs, or refactoring event-driven services.
- ▌ Skill Scout · livelybugSearch existing local, marketplace, GitHub, and web skill sources before creating a new skill. Use when the user wants to create, build, fork, or find a skill for a workflow.
- ▌
- ▌
- ▌
- ▌ Canary Watch · livelybugUse this skill to monitor and verify a deployed URL after releases — checks HTTP endpoints, SSE streams, static assets, console errors, and performance regressions after deploys, merges, or dependency upgrades. Smoke / canary / post-deploy verification.
- ▌ Eval Harness · livelybugFormal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles
- ▌ Fal AI Media · livelybugUnified media generation via fal.ai MCP — image, video, and audio. Covers text-to-image (Nano Banana), text/image-to-video (Seedance, Kling, Veo 3), text-to-speech (CSM-1B), and video-to-audio (ThinkSound). Use when the user wants to generate images, videos, or audio with AI.
- ▌ Git Workflow · livelybugGit workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
- ▌ IOS Icon Gen · livelybug bundleGenerate iOS app icons as PNG imagesets for Xcode asset catalogs from SF Symbols (5000+ Apple-native) or Iconify API (275k+ open source icons from 200+ collections). Use when generating icons, creating icon assets, adding icons to asset catalog, or searching for icons for iOS projects.
- ▌ Jpa Patterns · livelybugJPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot.
- ▌ Messages Ops · livelybugEvidence-first live messaging workflow for ECC. Use when the user wants to read texts or DMs, recover a recent one-time code, inspect a thread before replying, or prove which message source was actually checked.
- ▌ Mle Workflow · livelybugProduction machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML systems beyond one-off notebooks.
- ▌ Perl Testing · livelybugPerl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology.
- ▌ Product Lens · livelybugUse this skill to validate the "why" before building, run product diagnostics, and pressure-test product direction before the request becomes an implementation contract.
- ▌ Research Ops · livelybugEvidence-first current-state research workflow for ECC. Use when the user wants fresh facts, comparisons, enrichment, or a recommendation built from current public evidence and any supplied local context.
- ▌ Rust Testing · livelybugRust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.
- ▌ Safety Guard · livelybugUse this skill to prevent destructive operations when working on production systems or running agents autonomously.