tpp

AI Community

Repo stars 547
License MIT
Author repo exiftool-vendored.js

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Work on a Technical Project Plan. Use when starting or continuing work on a TPP from _todo/. Make progress on the referenced Tec…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Required Reading First”, “Process”, “Project Conventions”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name tpp directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Required Reading First / Process / Project Conventions” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: AI
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 94 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @photostructure · MIT
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: No requirement detected
Detected OS requirements: macOS · Linux · Windows
Runtime requirements: Node.js
Detected file/system behavior: Read-only
Write / modify
Shell exec
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview tpp.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# 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:

- [CLAUDE.md](CLAUDE.md)
- [docs/SIMPLE-DESIGN.md](docs/SIMPLE-DESIGN.md)
- [docs/TDD.md](docs/TDD.md)
- [docs/TPP-GUIDE.md](docs/TPP-GUIDE.md)

## Process

1. Read the TPP from the path given (default: check `_todo/` for existing TPPs)
2. Read all documents listed in the TPP's "Required reading" section
3. Identify the current phase from the checklist
4. 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
5. Update the TPP with progress, findings, and any new lore
6. When done, move the TPP from `_todo/` to `_done/`

## Project Conventions

- Always run `npm run compile` before testing
- Use `??` (not `||`) for nullish coalescing
- Use `node:` prefix for Node.js imports
- Use `if (x != null)` not `if (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

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Required Reading First → Process → Project Conventions
terms    -> Research & Planning · Write breaking tests · Design alternatives · Task breakdown · Implementation · Review & Refinement · Final Integration · Review
files/cmd -> todo/ · npm run compile · npm test · npm run lint · done/ · node: · if (x != null) · if (x)
body sha256 -> 79e0a94ceb5e

Decide Fit First

Design Intent

How To Use It

Boundaries And Review

Work on TPP

Required Reading First

Process

Project Conventions

Discussion