makinari-obj-template-selection

Select a Vitrina or Generic Git base and align the working tree.

1|Updated May 8, 2025
One-click install
npx skills add https://github.com/Uncodier/API --skill makinari-obj-template-selection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: makinari-obj-template-selection
Source: https://github.com/Uncodier/API/tree/main/src/skills/makinari-obj-template-selection
Command: npx skills add https://github.com/Uncodier/API --skill makinari-obj-template-selection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This playbook solves the problem of starting work from the correct repository baseline by deciding whether to use a Vitrina or a generic app base, ensuring the team starts from the right foundation and that the decision is documented for auditability.

Core Features & Use Cases

  • Decision matrix-driven base selection between Vitrina and Generic app baselines.
  • Record the decision in the requirement instructions to preserve an auditable trail.
  • Align the sandbox working tree to the chosen baseline branch before any feature work.

Quick Start

Decide the Git base (Vitrina vs Generic) based on the requirement type and client intent, then record the decision and align the working tree.

Frequently Asked Questions about makinari-obj-template-selection

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

FAQPage Schema
How do I decide between a Vitrina or generic app base for a new Git branch?

Use a decision matrix workflow to evaluate the requirement type and client intent, selecting the Vitrina or generic app baseline to ensure the team starts from the correct foundation.

How do I align my sandbox working tree to a chosen Git baseline branch?

Align the sandbox working tree by applying the explicit base selection decision and checking out the chosen baseline branch before starting any feature work.

Why should I document Git base selection decisions in requirement instructions?

Documenting Git base selection in requirement instructions preserves an auditable trail, ensuring the baseline decision between Vitrina and generic app is recorded for team visibility.

When do I need to use a decision matrix for Git branching and base selection?

Use a decision matrix for Git base selection when choosing between Vitrina and generic app baselines, ensuring the repository starts from the right foundation based on requirement type.

Does this Git branching workflow work without additional dependencies?

Yes, this Git branching workflow operates without additional dependencies, using a standalone decision matrix to determine and align the working tree to the baseline branch.