Peter537

@peter537 source repo

15 skills
0 followers
17 hours ago last updated

▌
Docs Audit · peter537 bundle
Audit and rebuild software-repository documentation against implementation evidence. Use for comprehensive documentation audits or refreshes that may create, rewrite, move, merge, or delete README files and project documentation; reconcile documentation with code, tests, configuration, commands, and public interfaces; redesign documentation structure; update documentation-owned tooling and configuration; and add evidence-backed Mermaid diagrams. Do not use for ordinary prose drafting, proofreading, copyediting, tone or voice work, repository-only analysis, application-code changes, or dependency- and package-only installation or change requests.

0
installs
▌
Deep Planning · peter537 bundle
Research and clarify complex software changes before implementation. Use for architecture proposals, migrations and refactors, parity or retirement inventories, sequencing and dependency analysis, scope and tradeoff decisions, ADR candidates, acceptance gates, and other software work that needs repository evidence plus targeted user questions. Do not use for straightforward changes with an already decision-complete specification.

0
installs
▌
Diagnose Bugs · peter537 bundle
Diagnose and repair concrete, non-obvious local-repository or CI defects through authentic failure evidence, localization, falsifiable experiments, causal explanation, and regression verification. Use when the user clearly asks to diagnose or debug a specific bug, reproduce an observed defect, investigate a concrete failure, perform root-cause analysis, repair a flaky test or regression, or trace a build, integration, environment, data-dependent, or measured performance failure. Do not use merely because something is broken, throwing, failing, or slow; exclude quick error explanations, lists of possible causes without investigation, issue summaries, proactive code or performance audits, ordinary feature work, known trivial fixes, and active production or security-incident response.

0
installs
▌
Verify Change · peter537 bundle
Verify whether an already-completed local-repository or CI change satisfies its acceptance criteria through reproducible, layered evidence and complete cleanup. Use when the user clearly asks to prove, validate, acceptance-test, or end-to-end verify completed behavior. Do not use for implementing or repairing a change, running one named check, broad auditing, root-cause diagnosis, planning, UI-quality review, dependency work, active incidents, deployment, release, or publication.

0
installs
▌
Write Clearly · peter537 bundle
Draft, edit, proofread, audit, and apply human feedback to intentional prose stored in software repositories while preserving meaning, language, voice, and format. Use for tasks that materially create or change repository prose, including documentation, plans, policies, release notes, wording in comments or docstrings, UI copy, errors, CLI help, localization strings, articles, brand writing, and personal nonfiction; also use for plain-language, clarity, tone, audience-fit, house-style, or voice-matching requests in any language. Do not use for creating or maintaining authoritative repository verification context unless the task is limited to its wording; without an explicit `$verification-context` invocation, that remains ordinary repository work. Also exclude semantic source-comment health, stale-comment, TODO, commented-out-code, or machine-directive audits; code-only work; translation-only requests; summarization; data extraction; factual verification; and poetry or fiction unless explicitly invoked.

0
installs
▌
Comment Health · peter537 bundle
Audit and improve the semantic health of comments and docstrings embedded in source, tests, configuration, build files, and scripts. Use for clear requests to review or clean up misleading, redundant, stale, misplaced, missing, commented-out, TODO/FIXME, API-documentation, doctest, or tool-directive comments. Do not use for documentation sets, wording-only editing, broad code audits, generated or vendored content, fixture text where comment syntax is data, or executable-code simplification.

0
installs
▌
Prune Codebase · peter537 bundle
Prove and safely retire dead or obsolete repository surface, including unused symbols, files, exports, routes, handlers, assets, flags, experiments, shims, compatibility paths, and migration paths. Use for clear requests to find or remove dead code, retire obsolete behavior, clean up stale feature flags or migrations, or prune a codebase. Do not use for broad code audits, local C# or Python simplification, dependency removal, bug diagnosis, architecture redesign, feature work, or cleanup justified only by style.

0
installs
▌
Deep Code Audit · peter537 bundle
Perform evidence-backed, read-only audits of software repositories or scoped changes for correctness, security, maintainability, readability, state and data ownership, testability, performance, architecture, file organization, dependency risk, proportionate sensitive-data risk, accidental complexity, overengineering, and unnecessary implementation or change surface. Use for comprehensive codebase audits, security reviews, or deep review of a diff, branch, pull request, file, or subsystem. Do not use for dedicated bug diagnosis, dependency-only reviews, personal-data or repository-exposure audits, pre-addition supply-chain gates, dedicated source-comment health or codebase-pruning passes, dedicated C# or Python simplification, routine implementation, simple style feedback, or a narrowly specified fix that does not request an audit.

0
installs
▌
Chatgpt Research · peter537 bundle
Orchestrate reproducible, multi-source software and product research through ChatGPT Deep Research and verify the resulting evidence. Use for complex or ambiguous questions requiring synthesis across external sources, official-documentation comparison, vendor or standards evaluation, UI reference analysis, conflicting claims, or traceable capture sets with URLs, dates, and citations. Do not use for a single fact, one-document lookup, ordinary web search, or repository-only investigation.

0
installs
▌
Reduce Code Slop · peter537 bundle
Simplify explicitly scoped C# or Python code without changing its established behavior. Use for clear requests to remove unnecessary indirection or generated boilerplate, harden weak type handling, de-slop an implementation, perform a focused simplification review, or apply already-configured simplification enforcement. Do not use for broad repository audits, repository-wide dead or obsolete surface pruning, bug diagnosis, architecture migrations, feature development, formatting-only cleanup, dependency installation, UI or prose work, or other languages.

0
installs
▌
Audit Dependencies · peter537 bundle
Audit every software dependency and supply-chain input in a repository, including direct and transitive packages, nested projects and workspaces, build plugins, CI actions, container images, vendored code, submodules, and runtime-loaded extensions. Use for dependency or package reviews; before adding, installing, upgrading, replacing, or removing dependencies; when manifests or lockfiles change; or when checking exact resolved versions, vulnerabilities, provenance, integrity, licenses, malicious packages, dependency confusion, maintainer risk, or supply-chain attacks. Do not use for broad source-code audits unrelated to dependencies.

0
installs
▌
Audit Data Exposure · peter537 bundle
Perform read-only, redacted reviews of repositories, Git changes or ranges, paths, and subsystems for personal data, private records, credentials, developer-machine metadata, re-identifiable samples, anonymization failures, and disposable one-time migrations or conversions. Use only when the user explicitly requests a personal-data, privacy, anonymization, repository-leak, sensitive-data exposure, or disposable-migration review. Do not invoke merely because code is being committed, released, published, or open-sourced, and do not use for ordinary code audits, dependency reviews, performing dataset anonymization, legal-compliance opinions, or implementation work.

0
installs
▌
Maui Blazor Browser · peter537 bundle
Prepare, assess, implement, and verify safe browser-development paths for .NET MAUI Blazor Hybrid UI by reusing or creating a companion Blazor Web host, or by creating an isolated temporary browser harness around host-neutral Razor Class Library UI. Use when a MAUI Blazor Hybrid project needs browser inspection, browser-driven development, responsive or DOM verification, shared MAUI-and-Web UI, host-specific service adapters, or diagnosis of a browser host that prerenders but does not become interactive. Do not use for ordinary Blazor Web applications, native-only MAUI/XAML work, visual-polish-only requests, or browser testing unrelated to MAUI Blazor Hybrid.

0
installs
▌
UI Design And Polish · peter537 bundle
Design, audit, refine, redesign, create, and polish task-oriented product interfaces using repository evidence and rendered verification, including requests to correct generic, templated, homogenized, or insufficiently product-specific UI. Also use for direct requests to create or maintain persistent project design context from repository evidence and explicit human decisions. Use for dashboards, data tools, forms, settings, workflows, application shells, page hierarchy, UI copy when hierarchy or interaction context is in scope, responsive behavior, accessibility, interaction states, design-system consistency, Streamlit interfaces, and Blazor Web Apps. Do not use for backend-only work, ordinary non-UI framework tasks, comprehensive documentation maintenance, other documentation-only changes, image-only work, wording-only UI copy, or marketing, editorial, and commerce surfaces.

0
installs
▌
Verification Context · peter537 bundle
Create, assess, or maintain a repository's authoritative verification guidance from existing local evidence. Use only when the user explicitly invokes $verification-context to document verification commands, entrypoints, environments, fixtures, evidence limits, persistence boundaries, reset procedures, and cleanup. Do not use to execute acceptance verification, perform comprehensive documentation audits, plan unresolved behavior, add dependencies or harnesses, diagnose bugs, run one named check, or prepare a release.

0
installs

15 published skills