tpp
- Repo stars 547
- License MIT
- Author updated Live
- Author repo exiftool-vendored.js
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @photostructure · MIT
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- Node.js
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: tpp
description: Work on a Technical Project Plan. Use when starting or continuing work on a TPP from _todo/. Mak…
category: ai
runtime: Node.js
---
# tpp output preview
## PART A: Task fit
- Use case: Work on a Technical Project Plan. Use when starting or continuing work on a TPP from _todo/. Make progress on the referenced Technical Project Plan by determining the current runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Required Reading First / Process / Project Conventions” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Work on a Technical Project Plan. Use when starting or continuing work on a TPP from _todo/. Make progress on the referenced Technical Project Plan by determining the current runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Required Reading First / Process / Project Conventions” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Validate with a small run
Start with a small task and check whether the result follows “Required Reading First / Process / Project Conventions”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: tpp
description: Work on a Technical Project Plan. Use when starting or continuing work on a TPP from _todo/. Mak…
category: ai
source: photostructure/exiftool-vendored.js
---
# tpp
## When to use
- Work on a Technical Project Plan. Use when starting or continuing work on a TPP from _todo/. Make progress on the refe…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Required Reading First / Process / Project Conventions” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "tpp" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Required Reading First / Process / Project Conventions
rules -> SKILL.md triggers / order / output contract
runtime -> Node.js | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Work on TPP
Make progress on the referenced Technical Project Plan by determining the current phase and taking appropriate action.
Required Reading First
Before any work, read these documents:
Process
- Read the TPP from the path given (default: check
_todo/for existing TPPs) - Read all documents listed in the TPP's "Required reading" section
- Identify the current phase from the checklist
- Execute work matching that phase:
- Research & Planning: Explore code, read docs, summarize findings in TPP
- Write breaking tests: Write tests that fail, proving the problem exists
- Design alternatives: Propose options with pros/cons in the Solutions section
- Task breakdown: Create specific, verifiable tasks with file paths and commands
- Implementation: Write code, compile (
npm run compile), run tests (npm test) - Review & Refinement: Lint (
npm run lint), simplify, DRY up, remove dead code - Final Integration: Verify all tests pass, update docs if needed
- Review: Final check against SIMPLE-DESIGN.md principles
- Update the TPP with progress, findings, and any new lore
- When done, move the TPP from
_todo/to_done/
Project Conventions
- Always run
npm run compilebefore testing - Use
??(not||) for nullish coalescing - Use
node:prefix for Node.js imports - Use
if (x != null)notif (x)for boolean safety - No mocks in tests - use real ExifTool and actual image files
- Conventional Commits for commit messages
- Always ask before committing or pushing
Decide Fit First
Design Intent
How To Use It
Boundaries And Review