Load foundational Animus docs and explore topic-specific project documentation.
npx skills add https://github.com/Craigtut/animus --skill doc-explorer
Please help me install this Agent Skill. Skill: doc-explorer Source: https://github.com/Craigtut/animus/tree/main/.skills/doc-explorer Command: npx skills add https://github.com/Craigtut/animus --skill doc-explorer
Learners and developers often struggle to locate and synthesize comprehensive Animus project documentation. This Skill provides a guided way to surface and load foundational docs and topic-specific material to accelerate understanding and correct implementation.
Invoke doc-explorer with a topic to focus exploration after loading the foundational docs: product-vision and brand-vision.
High-intent search queries and answers about installing and using this skill.
To explore Animus project documentation, you can load foundational documents like product-vision and brand-vision first, then invoke topic-focused exploration to surface architecture, SDK, and workflow context from the /docs directory.
Understanding Animus heartbeat and persona features requires loading core project documents and following a strategy-driven navigation approach to assemble relevant context from the structured documentation index.
Guided documentation exploration is well-suited for onboarding new developers because it automatically loads foundational context and follows a structured index to accelerate understanding of system design and correct implementation.
Yes, the Animus documentation exploration strategy automatically loads core foundational documents, specifically product-vision and brand-vision, to anchor all subsequent topic-specific architecture and feature explorations.
Navigating Animus docs to minimize search overhead involves following the project's documented exploration strategy to identify relevant files, loading foundational documents first, then targeting specific workflow topics under /docs.
Strategy-driven navigation for Animus feature exploration relies strictly on project docs located under /docs, so its context-gathering capability is limited to the scope and completeness of those existing documentation files.
nklischDesign end-to-end test suites with golden-path and adversarial cases.
kevinslinIdentify review types and apply personas to produce structured critiques.
dmzoneillExplain code snippets with architectural context and similar implementations.
791994545Search installed Reasonix skills by keyword or list the skill directory.
