← all publishers

cmdr-chara

@cmdr-chara source repo

Report this profile Claim this profile

• 21 skills
• 0 followers
• 14 hours ago last updated

1. ▌
   Unlazy · cmdr-chara bundle

   Evidence-backed completion discipline for substantial tasks. Use when the user explicitly asks for exhaustive follow-through, every requested item finished, a long autonomous task to continue until measurable completion, or invokes unlazy, depth-tree, or gate-based execution. Do not use for trivial edits, factual questions, or to override a specialist skill's safety, approval, or release authority.
   0
   installs
2. ▌
   Bug Finder · cmdr-chara bundle

   Hunt for previously unknown correctness defects in an existing repository by deriving invariants, prioritizing high-risk surfaces, generating concrete bug candidates, and proving or retiring them with bounded evidence. Use when the user asks to find bugs, hidden defects, races, lifecycle failures, data-loss paths, or correctness problems without supplying a specific known symptom. Do not use for a known failure with an uncertain cause, a defined diff review, generic improvement prioritization, or release approval.
   0
   installs
3. ▌
   Toolchain Preflight · cmdr-chara bundle

   Resolve local shell, runtime, package-manager, browser, native-command quoting, and text-encoding constraints before repeated builds, tests, scripts, or browser checks. Use when required executables or invocation behavior are unknown, or when a task reports missing commands, blocked shims, incompatible runtimes, quoting failures, missing browser binaries, or encoding errors. Do not use as a mandatory gate when the repository's documented command already works, for causal application debugging, for dependency migrations, or for final release judgment.
   0
   installs
4. ▌
   Debugging Investigator · cmdr-chara bundle

   Diagnose a concrete failure through controlled reproduction, ranked hypotheses, minimally invasive instrumentation, causal tracing, and falsification, then recommend the smallest explanatory fix and regression test. Use when observed behavior is wrong and the cause is uncertain. Do not use for planned upgrades, broad refactors, feature design, or release approval.
   0
   installs
5. ▌
   Production Web Builder · cmdr-chara bundle

   Build or audit production web interfaces across architecture, rendering, components, data, forms, authentication boundaries, motion, accessibility, performance, responsive behavior, testing, observability, SEO, deployment, and final browser verification. Use when implementation quality and production behavior are the main decisions. Do not use for visual direction alone, literal screenshot reconstruction alone, mobile-platform selection, or unconditional package installation.
   0
   installs
6. ▌
   Product Design Director · cmdr-chara bundle

   Define or elevate product UX and visual direction through brief inference, brand evidence, user-flow and state reasoning, explicit design calibration, responsive systems, accessibility, and redesign critique. Use when the core decision is what the experience should communicate and how it should feel or behave. Do not use for literal screenshot reconstruction, routine frontend implementation, or production architecture without a design-direction question.
   0
   installs
7. ▌
   Repository Intelligence · cmdr-chara bundle

   Map a repository's architecture, ownership, dependency boundaries, risk hotspots, change impact, and likely edit conflicts with traceable evidence. Use when a task asks what exists, who or what owns it, what a proposed change can affect, or where parallel edits may collide. Do not use to delegate work, implement the change, diagnose a specific runtime failure, or approve a release.
   0
   installs
8. ▌
   Screenshot To Interface · cmdr-chara bundle

   Reconstruct a maintainable interface from screenshots or visual references through evidence capture, structural decomposition, asset handling, responsive inference, component boundaries, accessibility, and iterative visual comparison. Use when fidelity to supplied visual evidence is the primary requirement. Do not use for greenfield art direction, generic frontend production hardening, or copying assets without rights.
   0
   installs
9. ▌
   Review And Refactor Code · cmdr-chara bundle

   Review a defined diff or code area for actionable defects and integration risks, assess structural problems, and plan or execute behavior-preserving refactors through traceable evidence and incremental verification. Use when a user asks for code review, change-risk analysis, maintainability assessment, cleanup, decomposition, or refactoring. Do not use for general repository mapping, unknown runtime failures, version or schema migrations, security-only review, platform-wide production audits, or final release approval.
   0
   installs
10. ▌
    Verification And Release · cmdr-chara bundle

    Build a risk-based verification strategy and decide whether an integrated change is ready to release from traceable test, CI, coverage, operational, security, compatibility, and rollback evidence. Use when the question is what must be proven or whether a completed change can ship. Do not use to implement the feature, diagnose an unknown failure, or treat a green checkmark as sufficient evidence by itself.
    0
    installs
11. ▌
    Expo React Native Builder · cmdr-chara bundle

    Build or audit a production Expo and React Native application across Expo Router, development builds, native modules, state/data, persistence, offline behavior, animation/gestures, accessibility, testing, performance, security, observability, EAS builds/updates, and store release. Use when Expo/React Native is selected or already established. Do not use to choose the mobile platform or to assume Expo Go and a package list are production architecture.
    0
    installs
12. ▌
    Content Provenance Hygiene · cmdr-chara bundle

    Inspect and sanitize provenance or metadata surfaces in user-owned text, images, PDFs, and document containers through an optional local watermarks-remover service. Use when the user wants evidence-first removal of invisible Unicode, C2PA, EXIF/XMP, or document metadata. Do not use for detector evasion, authorship misrepresentation, CAPTCHA/access-control bypass, or unrelated rewriting.
    0
    installs
13. ▌
    Documentation Synchronizer · cmdr-chara bundle

    Detect documentation drift caused by code, API, schema, configuration, migration, UI, deployment, or operational changes and update all affected user and maintainer surfaces consistently. Use when behavior or contracts changed and documentation must be mapped, edited, and validated. Do not use to invent product behavior, write unrelated marketing copy, or replace implementation verification.
    0
    installs
14. ▌
    Flutter Production Builder · cmdr-chara bundle

    Build or audit a production Flutter application across architecture, state, routing, networking, serialization, persistence, offline-first behavior, platform integration, adaptive UI, accessibility, testing, performance, security, observability, and release. Use when Flutter is selected or already established. Do not use to choose Flutter versus Expo/native or to mandate packages independent of repository requirements.
    0
    installs
15. ▌
    Delegate With Mission Cards · cmdr-chara bundle

    Delegate independent, bounded repository work to specialized reader and writer subagents using mission cards, exclusive write ownership, staged fan-out, and parent-side verification. Use for parallel exploration, reviews, research, isolated implementation, tests, migrations, or security-sensitive work. Do not use when work is small, tightly coupled, ambiguous, or cannot be independently verified.
    0
    installs
16. ▌
    Typescript Quality Enforcer · cmdr-chara bundle

    Audit and strengthen TypeScript/JavaScript type-evidence and lint discipline, stage adoption of deterministic anti-slop Oxlint rules, and remediate approved violations without laundering diagnostics. Use when a repository needs stronger TypeScript/JavaScript quality enforcement, unsafe type escape-hatch cleanup, anti-slop adoption, or systematic reduction of casts, unknown/any contracts, module mocking, and boundary-parsing debt. Do not use when the primary task is a concrete bug investigation, a known dependency/runtime migration, a measured performance bottleneck, an ordinary bounded refactor, a non-TypeScript platform audit, or final release approval.
    0
    installs
17. ▌
    Codebase Improvement Planner · cmdr-chara bundle

    Discover and prioritize evidence-backed opportunities to improve an existing codebase when no specific change has been chosen yet, then recommend the highest-value next upgrade and optionally execute an approved bounded maintenance slice. Use when the user asks what should be improved, modernized, simplified, hardened, cleaned up, or upgraded across a repository. Do not use when the primary task is a known dependency/schema migration, a concrete bug investigation, a measured performance bottleneck, a defined code review/refactor, platform-specific production work, or final release approval.
    0
    installs
18. ▌
    Mobile Architecture Director · cmdr-chara bundle

    Select and shape an evidence-based mobile approach among Flutter, Expo/React Native, native iOS/Android, Kotlin Multiplatform, web-container, and other viable options using product, team, device, security, offline, performance, accessibility, and distribution constraints. Use when platform choice or mobile architecture direction is unresolved. Do not use to implement an already selected Flutter or Expo application.
    0
    installs
19. ▌
    Multi Agent Work Coordinator · cmdr-chara bundle

    Plan and govern safe parallel repository work using a dependency graph, exclusive write ownership, overlap detection, integration order, and evidence-based acceptance of subagent results. Use when multiple bounded work items can proceed independently after repository boundaries are known. Do not use for repository discovery, role/model routing alone, tightly coupled work, or tasks too small or ambiguous to verify independently.
    0
    installs
20. ▌
    Codebase Evolution Controller · cmdr-chara bundle

    Control dependency upgrades, framework migrations, schema or API transitions, compatibility windows, staged rollouts, rollback, and removal of legacy paths using current evidence. Use when a repository must move from a known current state to a defined target state without breaking consumers. Do not use to diagnose an unexplained failure, perform an ordinary feature change, or make the final release-readiness decision.
    0
    installs
21. ▌
    Optimize Codebase Performance · cmdr-chara bundle

    Measure, diagnose, propose, and execute bounded performance improvements for latency, throughput, CPU, memory, GPU, I/O, startup, database, bundle, rendering, or infrastructure cost while preserving correctness. Use when a user asks to profile a critical path, explain a bottleneck, reduce resource use, or optimize measured performance. Do not use for unmeasured cleanup, incorrect behavior whose cause is unknown, version migrations, general platform audits, or final release approval.
    0
    installs