perhapsspy

@perhapsspy source repo

13 skills
0 followers
7 hours ago last updated

▌
Source Owner Audit · perhapsspy bundle
Use for read-only source-of-truth audits: identify the current code, API, config, doc, or behavior to follow; compare a proposed, migrated, ported, or current change against it; and report evidence, mismatches, unresolved decisions, and owner-level recommendations.

0
installs
▌
Project Context · perhapsspy bundle
Resume, handoff, and long-running repo work by keeping durable context across threads or agents: task briefs, logs, and reusable reference notes.

0
installs
▌
Project Context Migration · perhapsspy bundle
Audit scattered repository docs and notes, then move only the right working context into the `project-context` structure.

0
installs
▌
Structure First · perhapsspy bundle
Use for code generation, feature work, bug fixes, refactoring, and code review when a change creates or reshapes a multi-step flow, state lifecycle, side-effect or decision ownership, cross-unit composition, or boundary contract. Also use it when an existing structural problem makes those elements hard to trace or verify. Structural change is optional. Mechanical edits, throwaway experiments, and coherent local changes stay with their current owner and focused verification.

0
installs
▌
Tighten Docs · perhapsspy bundle
Use by default whenever creating, revising, reviewing, or finalizing human-authored documentation whose source meaning is settled, including documentation changed within another task. Apply from first draft through final review to keep one direct current state, clear reader routes and ownership, and remove rejected decisions that survive as negation or defensive prose. Skip prose-free mechanical edits, unresolved meaning, append-only history, generated artifacts, pure translation or localization, and always-read instruction design.

0
installs
▌
Agents Md Editor · perhapsspy bundle
Use when creating, editing, or reviewing AGENTS.md, agents.md, CLAUDE.md, Copilot instructions, Cursor rules, or any always-read repository instruction file. Keep persistent agent instructions small, durable, non-duplicative, and action-oriented; classify content that belongs in commands, onboarding, reference docs, handoff state, enforcement, or removal instead of preserving it in always-read files.

0
installs
▌
Chatgpt Pro Reasoner · perhapsspy bundle
Use only when the user explicitly invokes $chatgpt-pro-reasoner to send a focused thinking problem to ChatGPT Pro through the Codex in-app browser. Treat ChatGPT Pro as an external reasoning head, and keep consultations in one dedicated Codex Reasoner ChatGPT project that the skill initializes on first use.

0
installs
▌
Codex Project Director · perhapsspy bundle
Invoke explicitly with $codex-project-director to act as an active, non-implementing control plane that drives multiple Codex tasks or sessions toward one verified project outcome. Use only for a user-designated director or supervisor session, not a single local task, ordinary implementation, one-off review, or status summary.

0
installs
▌
Codex Token Discipline · perhapsspy bundle
Use for Codex work with clear excess-cost risk: broad or unpredictable logs and diffs, browser/UI loops, costly execution/retry loops and progress observation even with small output, subagents, repeated compaction, or explicit usage audits. Guides bounded execution and observation, preflight output limits, bounded delegation, evidence reuse, and compact checkpoints. Skip routine edits and direct answers. Routine test runs alone are not a trigger.

0
installs
▌
Interactive State Flow · perhapsspy bundle
Use when an interactive flow is laggy, stale, or race-prone because user intent, source state, derived presentation, async IO, scheduling, or background work are mixed. Keep source state prompt, protect the urgent interaction path, and admit async or presentation results only through a freshness-owning boundary.

0
installs
▌
Justified Change · perhapsspy bundle
Use for non-trivial code-change planning, implementation, bug fixes, refactors, review edits, and diff reviews where scope decisions such as fields, options, abstractions, or follow-ups must be necessary, goal-proportional, evidence-backed, and verifiable without speculative work

0
installs
▌
Purpose First Design · perhapsspy bundle
Use when product meaning or implementation-planning direction is materially open before solution structure is settled, including early direction for a new feature, reuse choices, temporary implementations, or another materially consequential product or implementation-planning choice. Choose a bounded provisional direction from user/domain purpose, locked decisions, explicit constraints, authority, current evidence, and observable success. Do not use for settled code structure, implementation execution, source discovery, or document editing.

0
installs
▌
Semantic Boundary Design · perhapsspy bundle
Use when cross-layer feature, migration, integration, port, refactor, review, bug fix, or design planning needs one owner for user/domain meaning across UI, route, client state, command, API, storage, realtime, adapter, or presentation layers. Trigger for identity aliases, lifecycle/status, permissions/capabilities, route/query grammar, command payloads, result/event projection, freshness/fallback/revision semantics across representations, compatibility translation, duplicated meaning rules, or multiple representations of the same user/domain meaning. Do not use for read-only owner discovery, local flow cleanup after owners are clear, pure async responsiveness/freshness work, or scope-control alone.

0
installs

13 published skills