living-docs
Living Docs
Generate documentation driven by current code reality and verified changes. Every document traces to specific files and, when relevant, commits.
Philosophy
Documentation must be:
- Accurate: derived from code and commits, not imagination
- Navigable: a human or agent can find what they need in 1-2 hops
- Maintainable: updating docs is a natural part of the development flow
- Dual-audience: useful for both humans reading markdown and agents consuming context
- Co-located: per-service docs live with the service code they describe
Language policy: Generate all documentation in English. Include Spanish translations in the aliases frontmatter field.
Technology-Agnostic Principle
The skill must infer architecture from evidence, not from framework assumptions.
More from rcrespo-tripulse/tripulse-skills
sap-business-one-servicer-layer-sql
SAP Business One Service Layer (b1s/v1 and sml.svc) integration guide for authentication/session cookies, OData query options, QueryService crossjoin filtering, semantic-layer aggregation, and multipart $batch orchestration. Use when building or debugging SAP B1 Service Layer HTTP calls, including metadata discovery, SQLQueries/* endpoints, and b1s.conf or per-request B1S-* configuration.
10skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
5planning-with-files
Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
4typescript-advanced-types
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
4prompt-engineering-patterns
Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, improving LLM outputs, or designing production prompt templates.
4dev-specs
Provide reusable Markdown specification templates for software delivery, starting with a functional specification document. Use when asked to create, draft, fill, adapt, or standardize development specs, functional specs, technical specs, acceptance criteria, scope documents, or requirements documents for a feature, module, API, workflow, or project.
1