agentleFS
cmdr-characmdr-chara/chara-toolkit/skills/llms.txt

chara-toolkit / skills

llms.txt2 starsChanged 11 days agoMITView on GitHub

delegate-with-mission-cards: Model-agnostic Mission Control for bounded multi-agent work with portable reader/writer roles, explicit ownership, safe parallel waves, runtime-inherited model settings, and parent-side verification. repository-intelligence: Evidence-backed architecture, ownership, dependency, hotspot, change-impact, and edit-conflict mapping. multi-agent-work-coordinator: Safe work graphs for parallel tasks across code, documents, research, datasets, configuration, and other independently ownable resources. codebase-evolution-controller: Dependency, framework, schema, and API evolution with compatibility stages, rollout, rollback, and evidence. verification-and-release: Risk-based test strategy and evidence-backed release readiness decisions. debugging-investigator: Reproduction-first debugging with ranked hypotheses,…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
llms.txt
delegate-with-mission-cards: Model-agnostic Mission Control for bounded multi-agent work with portable reader/writer roles, explicit ownership, safe parallel waves, runtime-inherited model settings, and parent-side verification.
repository-intelligence: Evidence-backed architecture, ownership, dependency, hotspot, change-impact, and edit-conflict mapping.
multi-agent-work-coordinator: Safe work graphs for parallel tasks across code, documents, research, datasets, configuration, and other independently ownable resources.
codebase-evolution-controller: Dependency, framework, schema, and API evolution with compatibility stages, rollout, rollback, and evidence.
verification-and-release: Risk-based test strategy and evidence-backed release readiness decisions.
debugging-investigator: Reproduction-first debugging with ranked hypotheses, causal tracing, minimal fixes, and regression design.
documentation-synchronizer: Code-to-documentation drift detection and synchronized user, developer, API, configuration, migration, and operations updates.
product-design-director: Product UX and visual direction, brand extraction, responsive systems, accessibility, redesign audits, and taste calibration.
screenshot-to-interface: Maintainable reconstruction from screenshots with structural analysis, asset handling, responsive inference, accessibility, and visual fidelity loops.
production-web-builder: Production web architecture and implementation across data, forms, motion, accessibility, performance, testing, observability, SEO, and browser verification.
mobile-architecture-director: Evidence-based selection among Flutter, Expo/React Native, native, and other mobile approaches.
flutter-production-builder: Production Flutter architecture and implementation across state, routing, data, offline, platform integration, testing, performance, and release.
expo-react-native-builder: Production Expo/React Native architecture and implementation across routing, builds, updates, native modules, data, offline, testing, performance, and stores.
review-and-refactor-code: Evidence-first PR/diff review with risk-adjusted depth, challenged findings, bounded re-review, and approval-gated behavior-preserving refactoring.
optimize-codebase-performance: Measurement-first performance diagnosis and bounded optimization with comparable benchmarks and approval before edits.
codebase-improvement-planner: Repository-wide improvement discovery that classifies Major, Medium, and Minor opportunities, ranks them by evidence and value, recommends the best next upgrade, and stops for approval before broad edits.
typescript-quality-enforcer: JavaScript/TypeScript only: evidence-backed type-safety audits, staged adoption of the bundled chara-lint Oxlint rules, anti-laundering remediation, and permanent lint/type-safety enforcement.
content-provenance-hygiene: Evidence-first inspection and authorized sanitation of provenance and metadata surfaces in user-owned text, images, PDFs, and document containers using locally available inspectors, with approval gates and before/after verification.
completion-proof: Evidence-bound completion for substantial scoped tasks using a request-traced done contract, coverage rosters, reviewed falsifiable probes, final-candidate rechecks, and audited claims, keeping blocked and waived scope visible without overriding specialist safety or approval boundaries.
bug-finder: Evidence-backed hunting for previously unknown correctness defects using explicit invariants, high-risk surface prioritization, bounded proof/falsification, and clean handoff to causal debugging or the owning specialist.
toolchain-preflight: Narrow local execution-path resolution for unknown or broken shells, runtimes, package-manager shims, native quoting, browser capability, and text encoding before retrying builds, tests, scripts, or browser checks.
security-review: Focused security code review across trust boundaries, authorization, untrusted input, secrets, file/network handling, and business-logic abuse.
rust-engineering: Bounded Rust crate implementation and source-language ports with explicit API, ownership, runtime, compatibility, and configuration-specific verification contracts.
kotlin-engineering: Bounded Kotlin implementation and ports, with conditional coroutine/Flow, Android/Compose, and multiplatform build guidance and separate host/device evidence.
python-engineering: Python modules, services, bots, scripts, and local ports with callable/data compatibility, cancellation/resource ownership, interpreter, import, and packaging evidence.
cpp-engineering: Bounded C++ implementation and ports with lifetime/ABI contracts, target-scoped native build and sanitizer checks, and conditional Qt/QML ownership guidance.
swift-engineering: Swift packages, native bridges, and local ports with API/ARC/isolation contracts and conditional Apple-platform and Metal rendering evidence.
go-engineering: Bounded Go packages, services, CLIs, and ports with owned goroutines, context/error/resource contracts, and module/tag/cgo-specific verification.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.