poteto-principles
Apply Engineering Principles to Software Changes
Software changes can repeat avoidable design, debugging, and verification mistakes. This skill gives coding assistants explicit engineering principles for making simpler, better-supported decisions.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
Review the Skillstore skill "poteto-principles" from https://skillstore.io/skills/masseater-poteto-principles.md and its manifest at https://skillstore.io/api/skills/masseater-poteto-principles/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„poteto-principles“ wird verwendet. Two fixes changed retry timing, but the same workers still receive most of the load.
Erwartetes Ergebnis:
- Shared assumption: retry timing causes the imbalance.
- Next evidence: count work assignments per worker across repeated runs.
- If the same workers dominate, inspect assignment rules before changing timing again.
- Verify any correction with both per-worker distribution and end-to-end behavior.
„poteto-principles“ wird verwendet. Review a task model with a completion flag and an optional completion date.
Erwartetes Ergebnis:
- The model permits a completed task without a completion date.
- Represent open and completed tasks as distinct variants, with a required date for the completed variant.
- Parse external records at the boundary and test both accepted and rejected states.
„poteto-principles“ wird verwendet. Our API refactor adds an adapter, but all callers are internal.
Erwartetes Ergebnis:
- Confirm that no external users require compatibility.
- Inventory internal callers and migrate them in verifiable units.
- Remove the old API after caller migration and verify the new observable contract.
- Use an adapter only when a specific transition requires it, with an explicit removal condition.
Sicherheitsaudit
SicherAll 31 static findings are false positives involving Markdown backticks, software engineering prose, attribution metadata, or readable multilingual text. No evidence found of prompt injection, credential theft, unauthorized network execution, or concealed payloads in the reviewed files. Semantic findings and remediation are empty.
Risikofaktoren
⚙️ Externe Befehle (25)
🌐 Netzwerkzugriff (1)
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
https://skillstore.io/skills/masseater-poteto-principles/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/masseater-poteto-principles?utm_source=security_passport_badge)HTML-Badge
<a href="https://skillstore.io/skills/masseater-poteto-principles?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/masseater-poteto-principles/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Einbettungskarte
<iframe src="https://skillstore.io/embed/skills/masseater-poteto-principles.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
masseater. (2026). poteto-principles security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/masseater-poteto-principles/audits/1BibTeX-Zitat
@techreport{masseater-masseater-poteto-principles-2026,
author = {masseater},
title = {poteto-principles security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/masseater-poteto-principles/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "poteto-principles security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "masseater"
date-released: "2026-10-24"
url: "https://skillstore.io/skills/masseater-poteto-principles/audits/1"
identifiers:
- type: other
value: "skillstore:masseater-poteto-principles:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore-Score
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
Diagnose recurring failures
Use reproduction and evidence to identify a shared faulty assumption after repeated fixes fail.
Plan a coordinated API migration
Inventory internal callers, define verification boundaries, and remove the legacy path when compatibility requirements permit.
Review design and test quality
Assess domain models, validation boundaries, reader load, and whether tests assert observable behavior.
Diese Prompts ausprobieren
Review [change] using poteto-principles. Identify unnecessary complexity, unclear state, and missing verification. Explain your recommendations without editing files.
Investigate [bug] and these failed fixes: [attempts]. Reproduce the failure, identify shared assumptions, and propose the smallest root-cause fix with a behavioral regression test.
Plan migration from [old API] to [new API]. Inventory callers and compatibility requirements. Define reversible phases, verification boundaries, and conditions for removing the old API.
Review [workflow] for shared mutable state, retries, and partial failures. Propose isolation or serialization, reconciliation steps, and direct checks for repeated runs and interrupted execution.
Bewährte Praktiken
- Provide the relevant code, observed behavior, constraints, and verification commands before requesting recommendations.
- Define compatibility requirements and approval boundaries before planning migrations or autonomous edits.
- Keep reproduction steps, direct checks, and measurement evidence with each proposed change.
Vermeiden
- Applying every principle mechanically without checking project constraints or existing invariants.
- Removing validation before confirming that every external input is parsed at the correct boundary.
- Treating compilation, mock call counts, or agent reports as proof of correct user-visible behavior.
Häufig gestellte Fragen
What is poteto-principles?
Can I use it with Claude, Codex, and Claude Code?
Does the skill include scripts or an automated checker?
Is the guidance specific to TypeScript?
Does it allow irreversible actions without approval?
Does it include the linked benchmark checklist?
Entwicklerdetails
Autor
masseaterLizenz
MIT
Skillstore-Revision
r1
Versionshinweis
Der Autor hat keine Version angegeben.
Ref.
4884e8ca178242496c82c517dcebea18c1f716fd
Aktualität der Wartung
24.10.2026
Nutzung
0 Downloads · 0 Aufrufe
Dateistruktur
📄 encode-lessons-in-structure.md
📄 make-operations-idempotent.md
📄 migrate-callers-then-delete-legacy-apis.md
📄 outcome-oriented-execution.md
📄 redesign-from-first-principles.md
📄 separate-before-serializing-shared-state.md
📄 sequence-verifiable-units.md
📄 test-behavior-not-implementation.md
📄 SKILL.md