PARA Kit

Define the four-pillar PARA workspace structure and v1.6.3 project.md schema.

48|18|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/pageel/para-workspace --skill para-kit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: PARA Kit
Source: https://github.com/pageel/para-workspace/tree/main/templates/common/agents/skills/para-kit
Command: npx skills add https://github.com/pageel/para-workspace --skill para-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

PARA Kit helps you standardize a PARA workspace so both humans and AI agents can reliably understand project layout, read the right authority files, and follow kernel governance constraints without ambiguity.

Core Features & Use Cases

  • Workspace layout reference: Defines the four pillars (Projects, Areas, Resources, Archive) and the standard project folder anatomy (including sessions, artifacts, docs, and agent/project rule hooks).
  • project.md contract/schema: Documents the v1.6.3 YAML frontmatter fields and how agent rules/skills flags should be represented.
  • Kernel governance quick reference: Summarizes invariants (what must never be violated) and heuristics (how to behave safely and consistently) for predictable operations.
  • Selection strategy for execution: Clarifies when to use deterministic CLI commands versus agent workflows for multi-step reasoning tasks.

Quick Start

Use PARA Kit when you need to structure or audit a PARA workspace by asking the AI to validate a project.md and explain what files and rules the kernel expects.

Frequently Asked Questions about PARA Kit

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

FAQPage Schema
How do I structure a PARA workspace for AI agents?

To structure a PARA workspace for AI agents, implement the four-pillar directory model (Projects, Areas, Resources, Archive) alongside standard project folder anatomy for sessions, artifacts, and agent rule hooks. This ensures agents reliably understand project layout and read correct authority files.

What is the project.md frontmatter contract for workspace governance?

The project.md frontmatter contract defines v1.6.3 YAML fields specifying how agent rules and skills flags are represented. This schema standardizes project metadata so both humans and AI agents can load context and follow kernel governance constraints without ambiguity.

When do I need kernel governance constraints for agent context loading?

You need kernel governance constraints during planning and agent context loading to guarantee predictable runtime behavior. Kernel invariants define what must never be violated, while heuristics guide safe, consistent operations when agents interact with your workspace.

Can I use deterministic CLI commands instead of agent workflows for workspace auditing?

Yes, you can use deterministic CLI commands for straightforward workspace auditing tasks, while agent workflows handle multi-step reasoning. The selection strategy clarifies when to choose deterministic execution versus agent-driven parsing for optimal results.

Does PARA Kit work without external dependencies?

PARA Kit operates without external dependencies, providing a self-contained reference for workspace scaffolding and governance. It supplies the canonical structure and rules needed to organize projects consistently without requiring additional packages.

What's the best way to validate a project.md schema against kernel invariants?

The best way to validate a project.md schema is to ask the AI to check your file against the v1.6.3 frontmatter contract and explain what files and rules the kernel expects. This audits compliance with kernel-invariant constraints for predictable behavior.