CCDawn
- 30 skills
- 0 followers
- 17 hours ago last updated
- ▌ Briefbound Router · ccdawn bundleUse 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.
- ▌ Briefbound Planning · ccdawn bundleUse 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.
- ▌ Briefbound Goal Loop · ccdawn bundleUse when the user explicitly requests an open-ended, persistent iteration policy with evidence-based next-step selection and stop conditions, and no domain-specific research, score, development, or coordination owner already controls the loop.
- ▌ Briefbound Pr Review · ccdawn bundleUse 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.
- ▌ Briefbound UI Design · ccdawn bundleUse 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.
- ▌ Briefbound UI Review · ccdawn bundleUse 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.
- ▌ Briefbound Score Loop · ccdawn bundleUse 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.
- ▌ Briefbound Bug Review · ccdawn bundleUse 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.
- ▌ Briefbound Evaluation · ccdawn bundleUse when Briefbound workflow needs a Chinese-first evaluation adapter and no more specific existing skill already owns the review, debugging, PR, planning, feedback, verification, or goal task.
- ▌ Briefbound Creative Toolbox · ccdawn bundleUse when the user wants non-obvious but useful ideas, concept invention, naming, reframing, variation, selection, creative unblocking, or synthesis grounded in the current context.
- ▌ Briefbound Design System · ccdawn bundleUse 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.
- ▌ Briefbound Visual Design · ccdawn bundleUse 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.
- ▌ Briefbound AI Research Loop · ccdawn bundleUse 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.
- ▌ Briefbound Project Memory · ccdawn bundleUse when the user or project rules explicitly request project-local memory/dashboard initialization or updates, or when an existing `.docs/project-memory/` is needed for cross-session recovery, durable decisions, blockers, parallel-agent coordination, or formal handoff; do not auto-initialize or sync it for ordinary development.
- ▌ Briefbound Project Review · ccdawn bundleUse when Briefbound workflow needs a Chinese-first review of an entire repository, codebase, architecture, technical debt, test coverage, risk modules, maintainability, onboarding state, or project health before planning, refactoring, takeover, or prioritization.
- ▌ Briefbound Completion Summary · ccdawn bundleUse when completed work needs formal cross-stage or cross-session synthesis, resumed-task closure, durable handoff evidence, deferred-risk accounting, or an independent PR/release evidence package that the current owner's concise final response cannot represent.
- ▌ Briefbound Research Rigor Review · ccdawn bundleUse 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.
- ▌ Briefbound Bdd Tdd Development · ccdawn bundleUse 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.
- ▌ Briefbound Development Cleanup · ccdawn bundleUse 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.
- ▌ Briefbound Thread Coordination · ccdawn bundleUse 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.
- ▌ Briefbound Code Structure Guard · ccdawn bundleUse 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.
- ▌ Briefbound Frontend Engineering · ccdawn bundleUse 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.
- ▌ Briefbound Simplification Audit · ccdawn bundleUse when the user explicitly requests a repository/subsystem simplification audit, dependency-bloat review, or ranked removal plan, or when concrete evidence makes structural complexity the primary investigation; do not substitute it for ordinary project health review.
- ▌ Briefbound Simplification Review · ccdawn bundleUse 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.
- ▌ Briefbound Huawei Nslb Score Loop · ccdawn bundleUse when a Huawei Algorithm Challenge 37 NSLB workspace needs live status, adaptive solver search, comparable evaluation, packaging, or online-score feedback; it is a thin project adapter over briefbound-score-loop.
- ▌ Briefbound Feature Reuse Research · ccdawn bundleUse when a complex feature has an unresolved reuse decision and external projects, libraries, standards, examples, or in-project modules could materially change architecture, dependencies, scope, or implementation; do not use for routine work already covered by local patterns or standard platform capabilities.
- ▌ Briefbound Performance Engineering · ccdawn bundleUse 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, or an already-located N+1/local inefficiency whose batch fix and deterministic count verification are clear to the current owner.
- ▌ Briefbound Multi Agent Orchestration · ccdawn bundleUse when two or more existing, independent Codex App threads in the same project can help each other finish their own tasks through peer negotiation, shared-contract alignment, dependency exchange, conflict reduction, or coordinated local integration; do not use to create or command subagents, transfer ownership, or add ceremony to unrelated work.
- ▌ Briefbound Competition Research Lifecycle · ccdawn bundleUse 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.
- ▌ Briefbound Autonomous Collaboration Loop · ccdawn bundleUse 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.