Organize project knowledge into principles, domain mappings, and runbooks.
npx skills add https://github.com/iheCoder/Lib --skill project-cognition
Please help me install this Agent Skill. Skill: project-cognition Source: https://github.com/iheCoder/Lib/tree/main/skill/project-cognition Command: npx skills add https://github.com/iheCoder/Lib --skill project-cognition
This Skill provides a structured approach to capturing and organizing project-level knowledge across rules, domain relationships, and operational experience, preventing knowledge loss and accelerating onboarding.
Open the Project Cognition tool and add a new cognition entry following the Update Protocol.
High-intent search queries and answers about installing and using this skill.
Organize project knowledge using a three-layer model that captures project principles, maps domain knowledge, and codifies runbooks. This structured approach prevents knowledge loss and accelerates onboarding by storing rules, system relationships, and operational experience.
Document troubleshooting steps and maintenance checklists by creating runbooks within a project cognition structure. Runbooks collect practical command sequences and operational procedures, ensuring troubleshooting experience is codified and easily accessible for future maintenance.
Map domain knowledge by documenting system relationships, data flows, and key field definitions within a structured cognition model. This captures critical architecture context, ensuring system relationships are explicitly recorded for engineering reference and onboarding.
Yes, project knowledge management supports versioned updates through a frontmatter-driven structure and incremental writing rules. Users read an index file to determine where to place new cognitions, ensuring documentation evolves safely without overwriting existing context.
Yes, you can capture project constraints and validation requirements using a core manifest. This stores project principles and validation rules to guide changes, ensuring engineering teams respect existing constraints when modifying the codebase.
Use a three-layer model for indexing documentation when you need to separate project principles, domain relationships, and operational runbooks. This structured approach prevents knowledge loss better than flat wiki pages by ensuring incremental, versioned updates across distinct cognition layers.
MakisuoInstall and configure a local ClickHouse environment with clickhousectl.
KISHOR403Extract YouTube transcripts, metadata, and chapters into Markdown for Obsidian.
channgGenerate static documentation websites from markdown files with sidebar navigation.
TaylorHustonSynthesize multiple sources into structured documents with citations.
