무료GitHub에 공개

knowledge-priming

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

techygarg/lattice

설치 방법 보기

포함된 파일(1)

SKILL.md2.7 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Knowledge Priming

Config Resolution

Look for .lattice/config.yaml in the repo root.
If found, check paths.knowledge_base for a custom document path.
If a document exists at that path, read the full document.
STOP: Apply the loaded document as ambient context before any design, implementation, or review work begins.
If a path is configured but no document exists at it → tell the user which configured path is missing, then see "When No Document Exists".
If there is no config file or no paths.knowledge_base key → 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 — a guided interview (~10 questions) producing a concise document (~50 lines).

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

Do not block. Continue without the 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?"

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

같은 저장소의 스킬

architecture

무료

Enforce architectural rules when generating or modifying code, and validate proposed designs before approval (design mode). Defaults to clean architecture; supports any architecture style via the architecture-refiner. Validates layer responsibilities, dependency direction, and structural constraints using the loaded architecture rules. Use when generating code, reviewing architecture, creating new files, or when the user mentions 'architecture', 'layers', 'structure', 'dependency rules', 'hexagonal architecture', 'ports and adapters', 'modular monolith', or 'onion architecture'. Also use when reviewing generated code for structural compliance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

techygarg/lattice2062026년 10월 10일 업데이트

architecture-compass

무료

Architectural thinking partner for an existing repository — scans the codebase, conducts a structured interview, agrees on current architectural state and recommended direction, and produces a shareable insights document. Scoped to one repository, module, or folder. Does not execute transformation — it orients. Use when the user says 'assess my codebase architecture', 'what direction should my codebase go', 'architecture compass', 'understand my architecture', 'audit architecture drift', 'architectural assessment', or 'help me understand what is wrong with my codebase'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

techygarg/lattice2062026년 10월 10일 업데이트

architecture-refiner

무료

Facilitate a structured conversation to define architecture principles for a repository. Supports multiple architecture styles: clean architecture (default), hexagonal / ports & adapters, modular monolith, or custom. Produces a formal architecture document that the corresponding atom will use. Use when setting up a new project, defining architecture standards, or when the user says 'setup architecture', 'define layers', 'architecture principles', 'help me define my architecture', 'hexagonal architecture', 'modular monolith', 'ports and adapters', or 'define my architecture style'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

techygarg/lattice2062026년 10월 10일 업데이트

bug-fix

무료

Investigate, reproduce, and safely fix a bug with regression protection. Composes context, diagnosis, architecture, code quality, and testing guardrails into a reproduce-first repair workflow. Use when the user says 'fix this bug', 'debug this', 'investigate this failure', 'patch this regression', 'repair this issue', or 'why is this broken'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

techygarg/lattice2062026년 10월 10일 업데이트

clean-code

무료

Apply clean code principles when generating or modifying implementation code. Enforces function focus, naming clarity, complexity management, error handling, and self-documenting style. Use when the user mentions 'clean code', 'code quality', 'coding guidelines', or 'implementation quality'. Loaded automatically by the code-generating molecules (code-forge, refactor-safely, bug-fix). This skill governs the craft of writing individual code units -- not architecture (see architecture), not security posture (see secure-coding), not test structure (see test-quality), and not refactoring workflows (see refactor-safely).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

techygarg/lattice2062026년 10월 10일 업데이트

clean-code-refiner

무료

Facilitate a structured conversation to define clean code principles for a repository. Produces a formal clean-code.md document that the clean-code atom will use as its override. Use when setting up coding standards, defining code quality rules, or when the user says 'setup clean code', 'define coding standards', 'code quality principles', 'coding guidelines', or 'help me define my code standards'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

techygarg/lattice2062026년 10월 10일 업데이트

techygarg의 스킬 모두 보기

이 스킬의 문제 신고

설치

명령으로 설치

npx skills add https://github.com/techygarg/lattice --skill knowledge-priming

터미널에 붙여 넣고 실행합니다(Node.js 필요). Claude Code, Codex 등 설치할 에이전트를 고를 수 있습니다.

에이전트에게 부탁하기

다음 Agent Skill을 설치해 주세요.
https://github.com/techygarg/lattice/tree/main/skills/knowledge-priming

먼저 SKILL.md와 첨부 파일의 내용을 확인해 수상한 처리(외부 전송, 인증 정보 읽기 등)가 없는지 확인한 뒤 Claude Code는 ~/.claude/skills/knowledge-priming/, Codex는 ~/.agents/skills/knowledge-priming/ 에 배치해 주세요.

이 문장을 그대로 Claude Code나 Codex에 보내면 내용을 확인한 뒤 설치해 줍니다.

GitHub에서 소스 보기

저장소: techygarg/lattice
스타: 206
포크: 15
카테고리: 개발
라이선스: MIT
원문 언어: 영어
최종 업데이트: 2026년 10월 10일

스킬은 에이전트를 위한 지시와 스크립트의 묶음입니다. cccskills는 내용의 안전성을 보증하지 않습니다. 설치하기 전에 내용을 확인하세요.