project-context

Documents repository layout, TypeScript/Zod standards, and Claude Code session data paths for agents.

1|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/eci-global/80HD --skill project-context-eci-global
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-context
Source: https://github.com/eci-global/80HD/tree/main/.claude/skills/project-context
Command: npx skills add https://github.com/eci-global/80HD --skill project-context-eci-global

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a concise, reusable project context framework for documentation agents, enabling consistent access to project structure, key standards, and Claude Code session data paths.

Core Features & Use Cases

  • Project Structure Reference: Documents the standard 80HD project layout including apps/, packages/, infra/, and docs.
  • Standards & Guidelines: Enforces TypeScript strict typing, runtime validation with Zod, and idempotent migrations for safe evolution.
  • Session Data Paths: Specifies locations for Claude Code plans, tasks, and transcripts to preserve context across sessions.
  • Use Case: A documentation agent asks for the current project conventions; this Skill supplies a ready reference to answer consistently.

Quick Start

Load the project context by referencing the Project Overview and Standards sections; use paths under the repository root or the claude store as documented.

Frequently Asked Questions about project-context

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

FAQPage Schema
How do I provide consistent project context for documentation agents?

To provide consistent project context for documentation agents, you can load a reusable framework that documents the repository layout, enforces TypeScript strict typing and Zod validation, and specifies Claude Code session data paths for repeatable tasks.

What is the standard repository structure for a TypeScript documentation project?

A standard TypeScript documentation repository structure includes dedicated directories for apps, packages, infra, and docs, alongside specified paths for storing Claude Code plans, tasks, and transcripts to preserve session data.

How do I enforce Zod validation and TypeScript strict typing for agent tasks?

You enforce Zod validation and TypeScript strict typing for agent tasks by loading a project context framework that supplies coding standards and guidance for plan transcripts, ensuring safe and repeatable documentation execution.

Can I use this project context framework with my existing Claude Code sessions?

Yes, you can use this framework with existing Claude Code sessions by referencing the documented repository root and claude store paths to preserve context and enable consistent agent behavior across multiple sessions.

What are the limitations of using a repository structure reference for agent guidance?

The limitation of using a repository structure reference is that it provides basic implementation depth, meaning it supplies static project context and path guidance rather than dynamically analyzing your codebase or executing runtime validations automatically.

How do I preserve Claude Code session data paths for documentation tasks?

You preserve Claude Code session data paths by referencing a project context framework that explicitly specifies locations for plans, tasks, and transcripts under the repository root or claude store.