All authors
Claude Skills by photostructure
github.com/photostructure24 skills0 installs83 views
- HandoffUpdate TPP for engineer handoff when context is running low. Use when ending a session, running out of context, or switching to a different task.Votes: 0GitHub stars: 8
- ReplanIterative deep planning with critiques and alternatives. Use when facing complex design decisions, cross-platform changes, native module modifications, or API changes requiring thorough analysis.Votes: 0GitHub stars: 8
- ReviewReview code for potential issues and improvements. Use when asked to review specific files, functions, or code sections.Votes: 0GitHub stars: 8
- TppWork on a Technical Project Plan. Use when starting complex features, cross-platform changes, native module modifications, or multi-session work that needs persistent context.Votes: 0GitHub stars: 8
- HandoffUpdate TPP for engineer handoff when context is running low. Use when ending a session, running out of context, or switching to a different task.Votes: 0GitHub stars: 8
- ReplanIterative deep planning with critiques and alternatives. Use when facing complex design decisions, cross-platform changes, native module modifications, or API changes requiring thorough analysis.Votes: 0GitHub stars: 8
- ReviewReview code for potential issues and improvements. Use when asked to review specific files, functions, or code sections.Votes: 0GitHub stars: 8
- TppWork on a Technical Project Plan. Use when starting complex features, cross-platform changes, native module modifications, or multi-session work that needs persistent context.Votes: 0GitHub stars: 8
- GitplanPlan and execute coherent Conventional Commit groupings for tangled working tree changes — multiple intertwined logical edits that need to be split into separate, reviewable commits.Votes: 0GitHub stars: 4
- HandoffUpdate the active Technical Project Plan for handoff when context is running low or the session is ending, so the next session continues instead of restarting.Votes: 0GitHub stars: 4
- ReplanIterative deep planning with critiques and alternatives. Use when facing complex design decisions requiring thorough analysis.Votes: 0GitHub stars: 4
- Review StagedWorkflow to review the staged Git diff for verified bugs and then prepare a clean Conventional Commit. Use when the user directly asks to review staged changes or prepare a commit proposal. Do not trigger on a direct commit instruction without a review request.Votes: 0GitHub stars: 4
- ReviewCode-review workflow for verified issues in specific files, functions, diffs, or code sections. Use whenever a review is requested, whether by the user or by another agent. Report findings; the requester decides what to do with them.Votes: 0GitHub stars: 4
- Second OpinionGet second opinions on freshly written code from fresh Codex and Claude reviewers, one small batch at a time, then settle every finding against ground truth before accepting or vetoing it. Use when requested, when project instructions require review before commits, or as part of an active review workflow after tests pass.Votes: 0GitHub stars: 4
- StageUse when committing work from the current session to stage ONLY hunks the session touched, not the entire file. Prevents accidentally staging unrelated uncommitted changes from other work.Votes: 0GitHub stars: 4
- Tpp OrchestrateWork through a queue of Technical Project Plans serially — delegate each to a TDD subagent, get a cross-model second opinion, empirically vet every finding, and make one coherent commit per plan. Use when executing a documented plan queue such as _todo/ or _feat-name/ for a port, migration, or multi-stage feature.Votes: 0GitHub stars: 4
- TppWork a Technical Project Plan to completion — read the plan, start from its current phase, work through its tasks until their acceptance tests pass, and update the plan as each task lands. Use when starting or resuming multi-session work tracked in a plan file.Votes: 0GitHub stars: 4
- Write ClearlyDraft and revise prose for clarity, precision, concision, unambiguous execution, and honest emphasis using Orwell's rules, classic composition principles, modern plain-language guidance, and a specialized standard for agent instructions. Use for documentation, explanations, reports, emails, UI copy, agent instructions, plans, reviews, specifications, handoffs, or any request to simplify, tighten, clarify, humanize, remove jargon, make text sound less machine-generated, or reduce ambiguous wor...Votes: 0GitHub stars: 4
- Project SetupSetup and hardening review for cross-platform modern-C++ (C++17) native projects, especially Node.js addons built with node-gyp / node-addon-api. Use when asked to "set up a native addon", "harden a C/C++ build", "review my binding.gyp", "add compiler hardening flags", "wire up AddressSanitizer/UBSan/TSan/clang-tidy", "set up cross-platform CI / prebuilds for a native module", or "make this native code maintainable". Produces an applicability-aware baseline gap analysis (Met / Gap / Not appli...Votes: 0GitHub stars: 4
- Resource ReviewTop-level memory- and resource-safety code review for modern C/C++ (C++17), including Node.js native addons (node-addon-api / Node-API). Use when the user asks to "review C++/C for memory safety", "find a memory leak", "why does this segfault", "check for use-after-free / double-free / buffer overflow / data race", "resource/handle/fd leak", "review this native addon", "N-API / node-addon-api review", or to check native code with AddressSanitizer/UBSan/TSan/Valgrind. Reports only defects back...Votes: 0GitHub stars: 4
- Project SetupSet up, assess, or improve stable Rust projects for idiomatic safe code, maintainability, strict but usable rustc/Clippy/rustfmt policy, Cargo workspace and feature design, MSRV/edition/toolchain management, testing and CI, unsafe/FFI boundaries, documentation, crates.io packaging, and release hygiene. Use when asked to create or review a Rust project or Cargo.toml, make a Rust codebase easier to maintain, configure strict lints, reduce or govern unsafe code, add Miri/fuzz/sanitizer checks, s...Votes: 0GitHub stars: 4
- Web Security HardeningSecurity best-practices and hardening review for JavaScript/TypeScript web and Electron desktop applications. Use when asked to harden an app, review security posture or secure defaults, assess OWASP ASVS or Electron security-checklist alignment, improve HTTP headers or CSP, review forms/input validation/sanitization/uploads, strengthen authentication/passwords/sessions/secrets, secure Electron windows/preloads/IPC/navigation/permissions/protocols/updates/packaging, or evaluate deployment/ope...Votes: 0GitHub stars: 4
- Web Security ReviewTop-level security code review for JavaScript/TypeScript web applications and Electron desktop applications. Use when the user asks to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", "is this secure?", or to review Node/Express/React/Vue/Next/Nest/Angular/Electron code for database/storage security, XSS, authentication, authorization (IDOR/BOLA), SSRF, CSRF, deserialization, secrets, crypto, renderer/preload/main-process boundaries, co...Votes: 0GitHub stars: 4
- FindFind the local coding-agent session that wrote the uncommitted changes in a file, or in a pasted snippet of changed code or comment text, and give a one-line command that resumes it. Prefers the session that authored the change over a review session. Use when asked which session, chat, thread, or agent made an edit, or how to get back to the session behind a change.Votes: 0GitHub stars: 4