Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

knowledge-priming

Estrellas163

Forks12

Actualizado18 de junio de 2026 a las 04:41

Load project-specific context -- tech stack, architecture overview, directory layout, trusted sources, and conventions -- so that all skills operate with awareness of what this project actually is. Use when a knowledge base document exists, or when the user asks about the project's tech stack, architecture, conventions, framework, directory layout, or says 'tell me about this project', 'what are we using?', 'what's our stack?', or 'what framework is this?'. Use the knowledge-priming-refiner to create a knowledge base document.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

techygarg

techygarg/lattice

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

Más de este repositorio

mismo repositorio

refiners-update

techygarg/lattice

Update existing Lattice standards after a significant change — the update-mode counterpart to lattice-init. Scans .lattice/standards/, asks what changed, and routes each affected standard to its refiner's revise mode, recording a git-native change note. Use when the user says 'update refiners', 'refiners update', 'our standards changed', 'update our standards', 'the architecture changed, update the standards', 'we switched languages, update the standards', 'revise standards after a big change', or 're-run the refiners'.

2026-07-05163

skill-align

techygarg/lattice

Audit and fix all Lattice documentation, README, docs/, PROJECT.md, GitHub issue templates, and CLAUDE.md to ensure they are fully aligned with the current skill inventory. Documentation drift is the most common source of user confusion in Lattice — a skill exists in the codebase but not in the docs, or a renamed skill leaves a stale reference in the bug report template. If you've made any change to skills/ and haven't run this, run it now. Use when the user says 'align docs', 'audit docs', 'update documentation', 'skill align', 'check docs are in sync', 'audit skill inventory', 'ensure docs are aligned', 'are the docs up to date', or 'what needs updating'. Standalone — does not call other skills.

2026-07-05163

context-anchoring

techygarg/lattice

Manage per-feature living documents that capture decisions, constraints, and reasoning across AI sessions during active development. Scoped to feature-level work — design, implementation, bugfix, refactor — not for codebase-wide assessments or product-wide specifications (those define their own document lifecycles). Handles creating new context documents, loading existing ones, and enriching them with new decisions. Use when starting a new feature, resuming work, making technical decisions, resolving questions, or when context needs to persist across sessions. Use this skill whenever the user mentions 'load context', 'update context', 'context doc', 'decisions', 'continue where we left off', 'what did we decide', or 'capture this decision'.

2026-07-05163

design-blueprint

techygarg/lattice

Run a complete design workflow -- from establishing context through 5 progressive design levels to an approved blueprint. Composes context anchoring, design-first methodology, architecture, and DDD into a unified process. Handles both new features (create context doc) and resuming existing work (load context doc). Use when starting a design, planning architecture, or when the user says 'design a feature', 'blueprint', 'start designing', 'plan the architecture', or 'let's design before coding'.

2026-07-05163

lattice-init

techygarg/lattice

Guided setup and upgrade-check experience for Lattice projects -- scans the repository, detects existing configuration and outdated conventions, suggests refiners and available upgrades in priority order, and creates or reconciles the .lattice/ config. Bridges the gap between installing skills and getting first value, and between upgrading Lattice and adopting its newest conventions. Use when the user says 'lattice init', 'set up lattice', 'initialize lattice', 'get started with lattice', 'configure lattice for this project', 'check for lattice upgrades', or 'upgrade lattice conventions'.

2026-07-05163

requirement-forge

techygarg/lattice

Generate structured feature specifications through a collaborative product interview. Acts as a senior PM and business analyst pair — arrives with a point of view, challenges scope, proposes options at every decision. Composes the requirement-quality atom for spec quality enforcement and collaborative-judgment for surfacing genuine decisions. Produces an epic/feature hierarchy in .lattice/requirements/ that serves as direct input to design-blueprint. Use when the user says 'forge requirements', 'write requirements', 'spec this feature', 'create a feature spec', 'define this epic', 'write a PRD', 'spec out what we are building', or 'requirement forge'.

2026-07-05163

name

knowledge-priming

description

Knowledge Priming

Config Resolution

Look for .lattice/config.yaml in repo root.
If found, check paths.knowledge_base for custom doc path.
If doc exists at that path, read the full document.
STOP: Apply the loaded document as ambient context before any design, implement, or review work begins.
If no config, path, or doc found → see "When No Document Exists".

When No Document Exists

Inform the user:

No project knowledge base found. AI skills will operate from generic assumptions about tech stack, architecture, and conventions.

To create one, trigger knowledge-priming-refiner — guided interview (~10 questions) producing a concise document (~50 lines).

Can also create .lattice/standards/knowledge-base.md manually and reference in .lattice/config.yaml under paths.knowledge_base.

Do not block. Continue without knowledge base.

What the Document Contains

#	Section	What It Captures
1	Architecture Overview	App type, major components, how they interact
2	Tech Stack and Versions	Specific technologies with version numbers, including "not X" clarifications
3	Curated Knowledge Sources	Official docs, trusted blogs, internal references (5–10 max)
4	Project Structure	Directory layout showing where things live
5	Project Conventions	Project-specific conventions other skills cannot infer from code

Scope Boundary

Concern	Owned By
Coding style, naming principles, function design	clean-code atom
Architectural layers, dependency direction	architecture atom
Domain modeling, aggregate design	domain-driven-design atom
Input validation, injection prevention	secure-coding atom
Test structure, assertion quality	test-quality atom

Knowledge priming answers "what are we working with?" — not "how should we write?"