Use this skill for reproducing, maintaining, monitoring, releasing, or upgrading the WEIPINGCOUNCIL project. It enforces the full lifecycle path from planning through design, development, testing, release, maintenance, monitoring, and continuous upgrade against real open-source quality bars.
Instructions for appleweiping/WEIPING_COUNCIL, covering weipingcouncil agent instructions, source of truth, boundaries, weiping constellation and validation.
Use this skill for non-trivial work on WEIPINGWHALE (including its legacy deepseek CLI alias), especially release-level improvements, runtime honesty, safety, MCP, memory, terminal UX, packaging, or documentation.
Multi-agent paper review loop simulating top-venue peer review. Iterates until the paper passes quality gates. Use when user says "auto-review", "自动审稿", "review loop", "review the paper", or after paper-write produces a draft.
Systematic audit of all citations in a paper draft. Checks completeness, recency, fairness, and correct attribution. Use when user says "citation-audit", "引用审核", "check citations", "audit references", or as part of the pre-submission checklist after auto-review-loop passes.
Rigorous audit of experiment results before they become paper claims. Checks statistical validity, reproducibility, fair comparison, and evidence quality. Use when user says "experiment-audit", "审核实验", "audit results", "check my results", or after run-experiment produces results that need validation.
Bridge from experiment plan to executable code. Translates the experiment plan into runnable scripts, configs, and infrastructure. Use when user says "experiment-bridge", "实验桥接", "bridge to code", "implement the experiment", or after experiment-plan is complete and reviewed.
Rigorous experiment planning that produces a complete, auditable experiment plan with blocks, baselines, milestones, decision gates, and compute estimates. Use when user says "experiment-plan", "实验计划", "plan experiments", "design experiments", or after research-refine is complete and the research question is…
Final pre-submission audit verifying every claim in the paper is backed by valid evidence. The last gate before submission. Use when user says "paper-claim-audit", "论文声明审核", "final audit", "pre-submission check", or as the final ARIS step before submission.
Structured academic paper writing following top-venue conventions. Produces publication-ready LaTeX with proper structure, claims backed by evidence, and clear narrative. Use when user says "paper-write", "写论文", "write paper", "draft the paper", or after experiment-audit passes.
Disciplined idea refinement for research projects. Takes a raw idea and stress-tests it into a publishable research question with clear novelty, feasibility, and positioning. Use when user says "research-refine", "refine idea", "打磨想法", "refine this research direction", or presents a raw research idea that needs…
A decision-making framework based on the public work and ideas of Lidang, presented as a first-person perspective. It focuses on mapping goals into paths, constraints, costs, risks, and practical next steps.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
Create 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.
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUSLANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine…