All authors
Claude Skills by CCDawn
github.com/CCDawn37 skills0 installs30 views
- Briefbound Score LoopUse when repeated work is governed by an explicit metric, active baseline, candidate search, promotion rule, leaderboard feedback, or submission iteration; do not use for a one-off research check that its current owner can execute directly, or for non-competition performance optimization and profiling.Votes: 0GitHub stars: 6
- Briefbound Creative ToolboxUse when the user wants non-obvious but useful ideas, concept invention, naming, reframing, variation, selection, creative unblocking, or synthesis grounded in the current context.Votes: 0GitHub stars: 6
- Briefbound Diagram DesignUse when creating or redrawing structured diagrams such as architecture, flowcharts, sequences, ER/UML, timelines or quantitative charts as HTML, SVG or PNG, including Mermaid, draw.io and Excalidraw imports; also use proactively as support when a substantive report contains relationships, sequence, causality or quantitative comparisons that a diagram would make materially easier to understand. Not for photos, illustrations, UI screenshots, general image editing or routine short status reports.Votes: 0GitHub stars: 6
- Briefbound Autonomous Collaboration LoopUse when the user explicitly enables an automated same-project multi-thread development loop that keeps peer Codex tasks progressing, recovers conflicts or stale coordination, integrates verified work into local main, and closes cleanup without repeated gates; do not use before opt-in, for one-off coordination, remote publication without permission, or subagent creation.Votes: 0GitHub stars: 6
- Briefbound Bdd Tdd DevelopmentUse when an already-defined new behavior or high-risk implementation contract needs a failing test before implementation, or the user explicitly requests TDD; diagnosed bugs stay with briefbound-bug-review, while simple or mechanical work uses targeted verification.Votes: 0GitHub stars: 6
- Briefbound Bug ReviewUse when an observed bug, correctness regression, failing test, build failure, abnormal behavior, or unresolved root cause needs Chinese-first diagnosis and bounded repair; obvious local inefficiency found during feature work stays with its owner, while measurable performance work uses briefbound-performance-engineering.Votes: 0GitHub stars: 6
- Briefbound Code Structure GuardUse when active development or explicit refactoring has concrete code-structure risk: a source file is accumulating independently changing responsibilities, a class/component/function is hard to navigate or test, repeated changes touch distant sections, or the user asks to split a giant file; do not use for line count alone, generated/vendor/migration/schema/fixture files, or cohesive modules that remain easier to maintain together.Votes: 0GitHub stars: 6
- Briefbound Design SystemUse when a frontend task primarily concerns cross-component design tokens, semantic theming, component APIs, variants and states, shared primitives, Storybook or library governance, Figma-to-code consistency, or a staged design-system migration; do not use for a single page, isolated styling fix, visual direction, or review-only task without a systemic ownership problem.Votes: 0GitHub stars: 6
- Briefbound Development CleanupUse when a verified or integrated software change has concrete temporary artifacts, generated noise, task-owned background processes or listeners, stale claims, merged local branches, disposable worktrees, or a known PR lifecycle state that requires deferred or post-merge local closeout, or when the user explicitly asks to remove development residue or old branches.Votes: 0GitHub stars: 6
- Briefbound Feature Reuse ResearchUse when a new capability is not already implemented in the project and an existing library, project, standard, or example could replace writing it from scratch; do not use for bugs, styling, mechanical edits, or work that follows an existing local pattern.Votes: 0GitHub stars: 6
- Briefbound Frontend EngineeringUse when an aligned UI contract or established project pattern needs production frontend implementation across components, layouts, interaction states, responsive behavior, accessibility, or runtime browser verification; do not use when the primary uncertainty is product direction, visual identity, design-system governance, or review-only findings.Votes: 0GitHub stars: 6
- Briefbound Multi Agent OrchestrationUse when two or more existing independent Codex App threads in the same project can benefit from bounded peer coordination through BRT trusted relay, while each thread retains its original task, permissions, branch, and completion responsibility.Votes: 0GitHub stars: 6
- Briefbound Performance EngineeringUse when an explicit performance goal, measurable regression, unresolved hot path, large workload, concurrency/cache/streaming decision, or latency/throughput/CPU/memory/I/O/bundle budget needs profiling and evidence-backed optimization; do not use for routine development, speculative cleanup, competition score iteration, or an already-located N+1/local inefficiency whose batch fix and deterministic count verification are clear to the current owner.Votes: 0GitHub stars: 6
- Briefbound Plain TalkUse when as the default style layer for user-visible replies in this workspace, when the user asks for 说人话、讲重点、少贴代码、降低阅读成本, says the reply is hard to read, or wants a short passage de-AI-flavored; constrains only how results are reported, never what work is done or written to files.Votes: 0GitHub stars: 6
- Briefbound PlanningUse when aligned requirements need a persistent or reviewable implementation plan, including a compact task graph only when independent deliverables, owners, dependencies, risk gates, or verification contracts make splitting valuable.Votes: 0GitHub stars: 6
- Briefbound Pr ReviewUse when the user explicitly requests review of a PR, diff, branch, commit range, merge readiness, or review feedback, or when a high-risk change has reached an explicit pre-integration review gate; do not trigger merely because ordinary development finished.Votes: 0GitHub stars: 6
- Briefbound Project DissectionUse when the user wants to understand or learn a repository through source-guided architecture explanation, a representative execution path, design tradeoffs and a reading route; not for risk-first project audits or isolated function questions.Votes: 0GitHub stars: 6
- Briefbound Project MemoryUse when the user or project rules request project-local memory/dashboard initialization or updates, or an existing `.docs/project-memory/` or resolved external `activePaths.memory` root is needed for cross-session recovery, durable decisions, blockers, parallel coordination, or formal handoff; never auto-initialize or sync for ordinary development.Votes: 0GitHub stars: 6
- Briefbound Project ReviewUse when Briefbound workflow needs a Chinese-first review of an entire repository, codebase, architecture, technical debt, test coverage, risk modules, maintainability, or project health before planning, refactoring, takeover, or prioritization. Do not use when the user has listed several goals and has not chosen among them, such as speed, structure, and interface.Votes: 0GitHub stars: 6
- Briefbound Readme OptimizationUse when the user asks to create, rewrite, or improve a repository README（优化 README、补仓库文档、开源准备、仓库简介）, or a repo lacks a usable README before handoff or release; analyzes manifests and source facts first, then produces an audience-appropriate Chinese-first README where every command and claim is traceable.Votes: 0GitHub stars: 6
- Briefbound RouterUse when Chinese-first active intent discovery, local context probing, user calibration before downstream skill selection, owner/workflow routing, continuation, permission inference, or multi-thread/conflict coordination is needed.Votes: 0GitHub stars: 6
- Briefbound Simplification AuditUse when the user asks for a repository- or subsystem-wide redundancy audit, removal of unnecessary abstractions or dependencies, or a ranked deletion queue across the codebase; do not use for a single diff or PR over-design check, which belongs to briefbound-simplification-review.Votes: 0GitHub stars: 6
- Briefbound Simplification ReviewUse when the user explicitly asks whether a diff, PR, branch, commit range, or proposed patch is over-engineered or can be made smaller, or when concrete evidence makes removable complexity the primary review question; do not attach it to every code review.Votes: 0GitHub stars: 6
- Briefbound Thread CoordinationUse when existing independent Codex App threads in one project need peer advice, target/ACK validation, file or runtime-process ownership and shared data-root arbitration, conflict recovery, discussion, merge coordination, status exchange, or native-thread handoff without creating subagents.Votes: 0GitHub stars: 6
- Briefbound Ui DesignUse when a Briefbound task needs a new or revised UI/UX direction, information architecture, interaction model, responsive behavior, accessibility decision, or implementable interface contract; do not use for review-only findings, production implementation of an accepted contract, backend work, or mechanical frontend edits.Votes: 0GitHub stars: 6
- Briefbound Ui ReviewUse when an existing page, isolated preview, component, screenshot, UI flow, visual change, or frontend implementation needs a Chinese-first UX, visual hierarchy, interaction-state, responsive, accessibility, design-system, or browser-runtime review; use as support for preview approval and UI-focused PR review, and do not trigger for creating a new design or implementing accepted fixes.Votes: 0GitHub stars: 6
- Briefbound Visual DesignUse when a UI task primarily needs a distinctive but context-appropriate visual direction, brand expression, typography, color system, composition, imagery, iconography, or motion language before implementation; do not use for information architecture, routine product UI, design-system governance, implementation of an accepted direction, or review-only findings.Votes: 0GitHub stars: 6
- Briefbound Ai Research LoopUse when AI/ML research engineering needs baseline reproduction, hypothesis-driven experiments, ablations, evaluation design, findings synthesis, research direction selection, plateau recovery, or a reproducible loop from a paper/repository/research question to evidence-backed results, or coordinating cross-stage research competitions and benchmarks.Votes: 0GitHub stars: 6
- Briefbound Competition Research LifecycleUse when coordinating an end-to-end research competition or benchmark program across multiple lifecycle stages such as rules, data, baseline, experiments, claims, and submission; use a stage owner directly for isolated work.Votes: 0GitHub stars: 6
- Briefbound Research Rigor ReviewUse when an AI/ML research result, baseline promotion, ablation conclusion, benchmark claim, paper claim, surprising finding, or high-cost next experiment needs an evidence-focused rigor review before it is accepted, generalized, published, or used to redirect the research program.Votes: 0GitHub stars: 6
- Briefbound Api ContractUse when a change touches an external contract surface - REST/GraphQL endpoints, request/response schemas, DB schema, events, or CLI arguments - and needs design, breaking-change analysis, versioning, or a migration path; do not use for general implementation planning, code review, or feature coding.Votes: 0GitHub stars: 6
- Briefbound Runtime OperationsUse when a deployed or local service fails to start, misbehaves at runtime, or needs deployment verification: environment-vs-code triage, the port/health/business evidence ladder, service lifecycle, or safe restart and rollback; do not use for source-code bugs, PR checks, or post-merge cleanup.Votes: 0GitHub stars: 6
- Briefbound Skill AuthoringUse when adding, changing, or removing a skill in the Briefbound package itself: contract structure, routing anchors, catalogs, test cases, validator budgets, and install refresh; do not use for ordinary project features or general documentation work.Votes: 0GitHub stars: 6
- Briefbound Test StrategyUse when tests or coverage are the primary unknown: backfilling tests for untested code, coverage gap analysis, choosing test levels, or selecting regression tests after a change; do not use for TDD of newly defined behavior, bug-fix verification anchors, or benchmark work.Votes: 0GitHub stars: 6
- Briefbound AdrUse when the user asks to record a settled architecture or technology decision as an ADR（写 ADR、记录决策、技术选型定案存档）, or a "why" trail is needed for a chosen design, an old decision must be superseded, or new work conflicts with a prior decision; do not use for options still under discussion, project status snapshots, or README writing.Votes: 0GitHub stars: 6
- Briefbound DeslopUse when the user asks to de-AI-flavor a finished Chinese text (article, doc, blog, release notes, report, paper): fix AI-style sentence patterns, jargon, rhythm and punctuation while preserving facts, numbers, conditions, promises and attributions, keeping the author's voice; do not use for conversational reply styling, README restructuring, or translation.Votes: 0GitHub stars: 6
- Briefbound Release VersioningUse when the user asks to cut a release, write or update a changelog, decide a semver bump, run pre-release checks, draft release notes, or prepare a rollback plan; do not use for single bug-fix execution, deployment or runtime operations, or contract compatibility analysis itself.Votes: 0GitHub stars: 6