By lynxlangya
Accelerate development workflows with structured skills for planning, debugging, code review, architecture documentation, and skill authoring. Provides evidence-gated methodologies to surface gaps, reproduce bugs, review diffs with blast radius analysis, and draw faithful architecture diagrams.
Internal authoring template and manual canary. Copy this directory to start a new techne skill.
Interrogate a written engineering implementation brief before work starts. Use when a user brings a ticket, PRD, design note, or substantive engineering task brief and wants to begin implementation planning; force every fixed rubric element to be accounted, cite present/weak claims against the brief, surface gaps, solution-as-goal traps, contradictions, and questions, then emit an intent-level plan. Do not use for bare one-line requests, non-engineering artifacts, code diff review, bug fixing, or execution itself.
Reproduce a behavioral bug before fixing it, record the failing probe, and verify the fix with the same probe. Use for bug reports, failing tests, crashes, hangs, regressions, wrong output, and observable behavior that should change.
Evidence-gated diff review for PRs, branches, commit ranges, staged code changes, and merge readiness checks. Use when an AI reviewer must review a concrete git-anchored diff, judge whether code is safe to merge, inspect a PR URL or branch, cross-examine PR or commit claims, account blast radius, or render approve/request-changes/blocked verdicts. Do not use for design-only review, whole-codebase audits, bug fixing, or code authoring without a git diff under judgment.
Draw a faithful architecture or structure diagram of a real codebase or project by scanning the actual repo, never guessing. Use for system architecture, request lifecycle, data model, state transitions, type structure, draw the architecture, map this project, 画架构图.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
τέχνη · /ˈtɛk.niː/ · "TEK-nee"
Ancient Greek for craft · skill · art: the practical know-how of making and doing, and the shared root of both technique and technology. Aristotle placed technē (knowing how) beside epistēmē (knowing that).
Skills and agents for the AI era.
Website: techne.wangyun.fan.
Chinese version: README-CN.md.
techne is a curated library of skills and agent assets for practical AI-era work. A techne skill is not a prompt snippet. It is a forced cognitive move: a small procedure that makes an AI collaborator investigate, judge, write, code, or ship in a way it often skips under pressure.
The project keeps one shared source of truth in skills/. Host-specific files
stay thin: Claude Code plugin metadata, Cursor and Gemini manifests, and install
instructions for Codex, Kimi, and other Agent Skills hosts all point back to the
same skill bodies.
The current seeded skills use the anchor-* prefix because each one anchors AI
work to evidence it cannot self-report or fake: a source tree, run ledger, git
diff, or written brief.
anchor-viz — investigate a real codebase by diagramming it. It routes one user
request across architecture, interaction, data-model, state-model, and
type-structure diagrams, then validates and builds a local viewer. See
skills/anchor-viz/README.md for detailed usage.anchor-repro — force bug fixes through a failing reproduction first, then verify
with the same probe after the fix. See
skills/anchor-repro/README.md for detailed usage.anchor-vet — force code review through computed scope, accounted blast radius,
verified claims/findings, and admissible verdicts before approving or
requesting changes. See skills/anchor-vet/README.md for
detailed usage.anchor-intake — interrogate a written engineering implementation brief before work
starts, accounting the fixed rubric, surfacing gaps/traps/questions, and
emitting an intent-level plan. See
skills/anchor-intake/README.md for detailed usage.Recommended: ask your AI agent. Paste this into Claude Code or Codex:
Install techne for my current agent by following https://github.com/lynxlangya/techne/blob/main/INSTALL.md, then verify the techne skills are available.
The agent reads INSTALL.md, detects your harness (Claude / Codex / Cursor / Gemini / Kimi), runs the right install path, and confirms the skill works.
Manual: per-harness commands and the universal npx skills fallback are in
INSTALL.md.
For Claude Code:
/plugin marketplace add lynxlangya/techne
/plugin install techne@techne-dev
/reload-plugins
For Codex:
npx skills add lynxlangya/techne -a codex -g -y
See WORKFLOW.md for the delivery process and ROADMAP.md for the product map.
Public-facing documentation is split by language:
README.md is the default English document.README-CN.md is the Chinese companion document.The same convention applies to skill usage guides when a Chinese version is
needed, for example skills/anchor-viz/README.md and skills/anchor-viz/README-CN.md.
npx claudepluginhub lynxlangya/techne --plugin techneNo description provided.
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
Utharn Buranasaksee's agent skills for real engineering — grilling, spec/ticket flows, TDD, code review, domain modelling and more. Plug-and-play, not vibe coding.
Editorial "Skill Author" bundle for Claude Code from Agentic Awesome Skills.
Workflow skills and shared instructions for coding agents.
Matt Pocock 面向真实工程工作的 agent skills:持续追问、spec/ticket flows、TDD、代码审查、领域建模等。即装即用,不是 vibe coding。