tp-delivery-standards

Enforce TP delivery constraints for a WinForms .NET Framework layered architecture project.

Updated Aug 24, 2026
One-click install
npx skills add https://github.com/aggutierrez98/TP-TD --skill tp-delivery-standards-aggutierrez98
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tp-delivery-standards
Source: https://github.com/aggutierrez98/TP-TD/tree/main/.agents/skills/tp-delivery-standards
Command: npx skills add https://github.com/aggutierrez98/TP-TD --skill tp-delivery-standards-aggutierrez98

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Academic TP (trabajo práctico) projects on .NET Framework WinForms often drift away from their documented stack, layered architecture, and delivery plan as features accumulate. This Skill keeps every code change, diagram, and document aligned with the mandatory TP constraints before a task is closed. ## Core Features & Use Cases - Stack and architecture enforcement: Validates changes against .NET Framework 4.7.2, WinForms, and the mandatory UI/BLL/REPOSITORIO/DAL/BE/SERVICIOS/ABSTRACCIONES dependency matrix. - Delivery checklist: Requires requirement identification, architecture alignment, documentation impact detection, visual control naming, and successful compilation before closing work. - PlantUML-only UML policy: Routes diagram work through an embedded PlantUML subskill and a central UML/use-case skill, storing .puml sources in the repo ordered by technical requirement. - Use Case: When implementing login with Singleton, bitácora auditing, or Composite-based permission profiles, the Skill flags impacted formal documentation and diagrams and blocks completion until the solution compiles. ## Quick Start Use the tp-delivery-standards skill to review my changes to the login and bitácora modules against the TP architecture and delivery checklist before I commit.

Frequently Asked Questions about tp-delivery-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a layered architecture in a WinForms .NET Framework project?▼

Apply a dependency matrix that constrains references between UI, BLL, REPOSITORIO, DAL, BE, SERVICIOS, and ABSTRACCIONES layers, and validate every change against it. This Skill loads the architecture rules and blocks completion when layer boundaries are violated.

What delivery checklist should a .NET academic TP follow before closing a task?▼

Identify the impacted technical requirement, align code with the layered architecture, annotate affected diagrams, detect affected documentation, verify visual control naming, and compile the solution successfully. Diagram updates happen on demand, not after every change.

Does this Skill support patterns like Singleton, Composite, and Observer?▼

Yes, it flags special attention areas from the delivery plan: Singleton for login sessions, Composite with recursion for permission profiles, and Observer for dynamic multi-language support. Changes in these areas trigger documentation and diagram impact review.

Can I use visual UML tools instead of PlantUML for TP diagrams?▼

No, the policy requires all new or modified UML to be authored in PlantUML with .puml sources stored in the repo, ordered by technical requirement. Visual tools cannot be the sole source of diagrams.

When should the embedded PlantUML subskill be loaded?▼

Load it only when the task actually involves creating, editing, converting, or validating PlantUML diagrams. Pure code changes that do not require diagramming should not load the subskill, keeping context usage minimal.