qingye-lab
- 15 skills
- 0 followers
- 13 hours ago last updated
- ▌ Setup Rootloom · qingye-lab bundlePlan, install, inspect, update, or roll back Rootloom Personal Core in a user's Codex home. Supports Skills-only, guidance, and the recommended personal preset. Use when the user explicitly asks for a Rootloom setup plan, installation, configuration, bootstrap, repair, audit, status, update, reduction, rollback, or removal. Never overwrite user-owned files without showing the plan and obtaining exact replacement authorization.
- ▌ Project Guidance · qingye-lab bundleCreate, refine, or validate repository guidance on explicit user request; preserve real-path scope, managed ownership, and unrelated content.
- ▌ Operating Code Review · qingye-lab bundleReview without editing; report evidence-backed defects by severity and disclose material verification gaps.
- ▌ Operating Coding Change · qingye-lab bundleComplete scoped code changes with proportional verification; load governed, Evidence, and external-action procedures only when needed.
- ▌ Project Memory · qingye-lab bundleInitialize, retrieve, and explicitly update the separate Rootloom Memory plugin's repository-owned architecture, risk, decision, and failure lessons. Use only when explicitly requested. Memory is experimental, advisory, and outside Rootloom Core.
- ▌ Hengmu · qingye-lab bundleUnified public entry point for Hengmu. Use when the user invokes $hengmu, cannot remember a focused Hengmu Skill name, asks what Hengmu can do, wants a read-only lifecycle or status explanation, or wants Hengmu to route a natural-language request for repository, AI-agent, mobile, or portfolio audit, finding verification, open or constrained design/specification, emerging technology-evolution assessment, solution comparison, remediation planning, or a deterministic quality gate. Chinese design, specification, and constraint requests route the same way.
- ▌ Architecture Quality Gate · qingye-lab bundleDeterministic architecture quality gate for verified review artifacts. Use in local checks or CI to validate architecture configuration, block configured confirmed severities, enforce review freshness, and honor explicit baselines or time-limited waivers. Never treats raw model findings as gate failures and never replaces finding verification.
- ▌ Mobile Architecture Audit · qingye-lab bundleSpecialized architecture audit for mobile applications, especially iOS and SwiftUI. Use when assessing local persistence, offline behavior, synchronization and conflicts, migrations, background execution, notifications, networking and caches, state ownership, privacy permissions, battery efficiency, or excessive client-side business logic. Extends rather than replaces the general project architecture audit.
- ▌ Project Architecture Audit · qingye-lab bundleEvidence-backed, persistent architecture audit and profile setup for one repository. Use when initializing `.architecture`, onboarding to a codebase, reviewing architecture health, preparing a refactor, investigating structural debt, or assessing module boundaries, ownership, contracts, resilience, security, observability, tests, deployment, and over-design. Automatically initializes missing project governance unless the user explicitly requests read-only work. Produces candidate findings for independent verification, not confirmed conclusions, fixes, or remediation plans.
- ▌ AI Agent Architecture Audit · qingye-lab bundleSpecialized architecture audit for AI-agent systems and AI-enabled products. Use for agent runtimes, tool-using workflows, memory systems, RAG, MCP integrations, long-running tasks, model routing, evidence tracking, human approval, evaluations, or systems exposed to prompt injection and model uncertainty. Extends rather than replaces the general project architecture audit.
- ▌ Portfolio Architecture Audit · qingye-lab bundleSystem-of-systems architecture setup and audit across multiple projects. Use when initializing `.architecture-portfolio` or reviewing duplicated capabilities, project boundary conflicts, technology-stack sprawl, shared infrastructure, cross-project data flows, hidden coupling, deployment and domain complexity, reusable components, or a one-year technical governance roadmap. Requires an explicit portfolio registry and does not replace per-project audits.
- ▌ Architecture Finding Verifier · qingye-lab bundleIndependently verifies candidate architecture findings against current code and repository evidence. Use after any project, AI-agent, mobile, or portfolio architecture audit; when a finding may be based on weak heuristics; or before remediation and quality gates. Filters false positives, deduplicates findings, recalibrates severity and confidence, and preserves an auditable decision trail without changing code.
- ▌ Architecture Solution Advisor · qingye-lab bundleCompare, design, specify, or constrain an architecture for a verified remediation Review or an approved Design Brief. Use for open or constrained target architecture, technology and pattern selection, ADR-like decisions, trade-off analysis, and bounded technology-evolution assessment. Required, preferred, and prohibited constraints are challenged inputs; they are not proof. Produce a decision and target architecture, never an implementation plan or code change.
- ▌ Architecture Remediation Planner · qingye-lab bundleConverts an accepted architecture decision into an executable, dependency-aware migration roadmap for confirmed remediation findings or an accepted open/constrained Greenfield target. Use for implementation slices, compatibility, data migration, deployment sequencing, observability, rollback, stop conditions, effort, and acceptance criteria. Produces a plan only; it does not choose architecture or implement changes.
- ▌ Architecture Knowledge Curator · qingye-lab bundleMaintains the plugin's architecture quality models, styles, patterns, technology profiles, reference architectures, migration guides, domain guidance, decision rules, machine rule packs, and evidence-provider registry. Use when adding or refreshing architecture knowledge, checking official-source freshness, reviewing framework capability claims, resolving duplicate or contradictory entries, or preparing a release whose decision knowledge may be stale. Does not audit a product or choose a product architecture.