mit einem Klick
TerranSoulApp
TerranSoulApp enthält 13 gesammelte Skills von TerranSyn, mit Repository-Berufsabdeckung und Skill-Detailseiten auf SkillsMP.
Skills in diesem Repository
Never block on CI. After any push to main (or a PR branch), immediately continue other work and hand CI off to a background agent that watches the run and, if it fails, diagnoses → reproduces → fixes → re-gates → re-pushes, looping until the branch is green. Keeps main green without the main loop ever waiting on a ~12-minute CI cycle.
Run a TerranSoul feature demo by DRIVING the live app via Playwright over CDP (WebView2 on 127.0.0.1:9222). Use this skill whenever the user types /demo or /demo <scenario> — e.g. /demo jd, /demo resume, /demo e2e, /demo show. Especially trigger for /demo jd, which automates TerranSoul end-to-end: attach 4 resume PDFs, quick-import, and ask in English/Vietnamese/Japanese which candidate fits a role.
Independent checker for loop- or agent-produced changes in this repo. Runs the CI-exact gate (vitest, vue-tsc, eslint, CI-exact clippy, full cargo test --lib) and enforces the never-regress benchmark floors. Default stance REJECT; never implements fixes itself.
Designs and runs agentic feedback loops instead of one-shot prompts. Use it when: (1) starting any coding task an agent will iterate on (bug fix, migration, refactor, integration debug), (2) the user asks to 'design the loop', 'set up validation', 'make the agent run until tests pass', or mentions loop engineering, (3) an agent session is thrashing — repeated edits to the same files with no progress, oversized diffs, or actions taken without observing results, (4) choosing the right feedback signal (tests vs compiler vs review vs runtime logs) for a task, (5) auditing why an autonomous coding loop failed (overfit-to-test, context drift, unsafe autonomy), (6) designing a STANDING loop — a scheduled maintenance loop with a triage skill, state file, worktree isolation, maker/checker split, budget, and human gates (daily triage, CI sweeper, changelog drafter), or running loop-audit/loop-init/loop-cost.
Check this repo's resource budgets before and after every loop run: bench-terminal caps, one-bench/one-MCP rules, cargo serial-build limits, and the /loop engine's seeded budgets. Enforces early exit when nothing is actionable and appends a run entry to loop-run-log.md.
Read loop-constraints.md at the start of every loop run and enforce every rule. Runs BEFORE triage or any action skill. Constraints are binding — they encode this repo's real push/merge, denylist-path, bench-purity, and human-gate rules.
Triage this repo's real work queue at the start of a loop run or session: read rules/milestones.md (session checkpoint + next not-started chunk), the top of rules/completion-log.md, git/CI status, and the MCP brain. Produces a concise prioritized findings report and updates STATE.md. Report-only unless a chunk is authorized.
Run a live investor/demo pitch where TerranSoul (the pet) narrates a web slide deck aloud. The pet starts hidden; when the presenter clicks 'Click to reveal!' on slide 4, it appears, thanks Darren, introduces itself, and presents slides 5–9 — including a 30s walk through its human-brain architecture and the by-the-numbers comparison.
Configures a harness. A meta-skill that defines specialized agents and creates the skills those agents will use. Use it when: (1) the user asks to 'configure a harness' or 'build a harness', (2) the user asks for 'harness design' or 'harness engineering', (3) building a harness-based automation system for a new domain/project, (4) restructuring or extending a harness configuration, (5) operating/maintaining an existing harness, e.g. 'harness checkup', 'harness audit', 'harness status', or 'agent/skill sync'.
End-to-end multilingual demo: generate English docs, ingest via CDP, ask questions in 13 languages via Playwright, verify TerranSoul replies in the matching language. Spec-driven loop until all pass.
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Execute the implementation planning workflow using the plan template to generate design artifacts.
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.