project-guide

Resolve logix architecture doc and code routes for Effect v4 tasks.

4|1|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/yoyooyooo/logix --skill project-guide-yoyooyooo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-guide
Source: https://github.com/yoyooyooo/logix/tree/main/.codex/skills/project-guide
Command: npx skills add https://github.com/yoyooyooo/logix --skill project-guide-yoyooyooo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill reduces the time spent searching for the latest architecture decisions, relevant historical context, and the exact code/docs landing points in the logix ecosystem.

Core Features & Use Cases

  • Shortest doc routing: Jump directly to the current SSoT, ADRs, standards, and archive baselines to get authoritative answers quickly.
  • Task-based drill-down: Map your intent (API spine, hot path, React semantics, domain packages, capabilities/control plane, verification, anchoring) to the exact documents and code folders to read next.
  • Effect V4-first alignment: Guides a consistent reading and verification order that prioritizes new facts and Effect v4 constraints while treating archive as background.

Quick Start

Ask the AI to produce the doc and code reading route for your current task by referencing the categories and “当前任务路由” table in the guide.

Frequently Asked Questions about project-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the latest architecture decisions and ADRs for Effect v4?

Architecture planning for logix requires mapping your intent to exact documents and code folders. This Skill provides a task-based drill-down workflow that guides you to the specific code and doc landing points to read next.

What is the best way to navigate logix documentation for daily development?

To navigate logix documentation for daily development, follow the prescribed doc route ordering that uses AGENTS.md for governance. This Skill maps your specific task to the exact docs and packages paths required for reading and verification.

How do I locate the specific code landing points for logix runtime and platform work?

Locating specific code landing points for logix runtime and platform work requires drilling down to the mapped docs and packages paths. This Skill provides a navigation workflow that resolves exactly where to find these code baselines.

Does this documentation navigation approach work with Effect v4 constraints?

Yes, this navigation approach supports Effect v4 constraints by guiding a consistent reading and verification order. It prioritizes Effect v4-first documentation while treating archive materials as background reference only.

How do I explore logix example domains and capabilities using the documentation route?

Exploring logix example domains and capabilities using the documentation route requires mapping your intent to the exact documents and code folders. This Skill supports example exploration and domain package verification through task-based drill-down.

Why should I use a structured doc route instead of searching the logix ecosystem directly?

Using a structured doc route instead of searching directly reduces time spent looking for historical baselines and exact code landing points. This Skill resolves where to find the latest logix architecture facts quickly and consistently.