template-manager

name	Template Manager
description	Facilitates access and usage of standard Conglomerate templates. Provides ready-to-use formats for other skills.
metadata	{"model":"inherit","version":"1.0.0","type":"utility-template-manager","group":"99-common-utils"}

📝 Template Manager (Global Templates)

This skill provides centralized access to the project's standardized templates. Its goal is to ensure that all artifacts generated by Skill Cells maintain consistent structure and quality.

Available Templates

Templates are found in skills/99-common-utils/templates/.

🏗️ Architecture and Design

Template	File	Usage
ADR	adr.md	Architecture Decision Records
Tech Spec	tech-spec.md	Detailed technical specifications

🔌 Backend and APIs

Template	File	Usage
API Endpoint	api-endpoint.md	REST/GraphQL definition
Data Model	data-model.md	Database schemas

🎨 Frontend and UI

Template	File	Usage
Component Spec	component-spec.md	UI component design
Page Spec	page-spec.md	Page/Screen structure

🧪 Quality and Testing

Template	File	Usage
Test Plan	test-plan.md	Testing strategy
Bug Report	bug-report.md	Standardized error reporting

📐 UI Style Rules (Responsive Mandate)

This Template Manager enforces a Strict Bootstrap 5.x Policy for any generated or managed UI code artifact.

1. Framework: Only Bootstrap 5.3+. Do not use Tailwind or others unless explicitly excepted.
2. Responsive: All templates must be fluid and use Bootstrap breakpoints (sm, md, lg, xl).
3. Optimization: Use utility classes to minimize custom CSS.
4. Component Specs: If a component specification (component-spec.md) is created, it must reference the corresponding Bootstrap classes and components.

Instructions for Orchestrators

When delegating a task that requires generating documentation or specifications, instruct your specialists to use these templates.

Instruction Example

"Please design the Login component using the component-spec.md template located in skills/99-common-utils/templates/."

Benefits of Using Templates

1. Consistency: All documents have the same format.
2. Completeness: Templates include sections often forgotten (e.g., accessibility, error handling).
3. Readability: Facilitates reading for humans and other agents.
4. Interoperability: Improves inter-group communication (e.g., Backend better understands Frontend requirements).