project-context

Document project conventions and architectural context for the Agent Platform codebase.

Updated Aug 23, 2026

Search Tags:#architecture #github #jira #workflows #branch-naming #project-conventions #agent-platform

Ready to run

npx skills add https://github.com/seanwachs/cursor-skills --skill project-context-seanwachs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-context
Source: https://github.com/seanwachs/cursor-skills/tree/main/.agents/skills/project-context
Command: npx skills add https://github.com/seanwachs/cursor-skills --skill project-context-seanwachs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shared context for the AP project that captures conventions, naming patterns, and architectural knowledge used across multiple workflows. Read this first before touching the codebase to align with project standards.

Core Features & Use Cases

Documented project identity: Jira site, Confluence space, and issue statuses to guide automation and ticketing.
Branch naming convention and architecture overview to keep PRs and deployments consistent.
Cross-skill reference: provides a central source of conventions used by other skills and workflows.
Use Case: when starting work on a feature, consult this skill to ensure PRs and tasks follow project standards.

Quick Start

Read this skill before creating PRs, triaging issues, or making changes to the AP codebase.

Frequently Asked Questions about project-context

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

FAQPage Schema

What are project conventions for managing the Agent Platform codebase?▼

Branch naming conventions for the Agent Platform project follow documented project identity rules tied to Jira and Confluence. This skill provides cross-cutting conventions to ensure branch creation, pull requests, and deployments align with project standards before touching the codebase.

How do I align pull requests with project standards in Jira and GitHub workflows?▼

Before creating pull requests or triaging issues, read this skill to ensure your work follows documented project identity, branch naming conventions, and architecture overview. It serves as the central source of conventions used by other skills and workflows across the Agent Platform codebase.

Can I use this skill for issue triage and architectural decisions in the Agent Platform?▼

This skill applies to issue triage, branch creation, PRs, and architectural decisions within the Agent Platform project. It provides documented project identity, issue statuses, and architecture overview to guide automation and ticketing workflows.

When do I need to consult shared architectural context before modifying the codebase?▼

Consult this skill before creating PRs, triaging issues, or making changes to the Agent Platform codebase. It captures naming patterns, architectural knowledge, and cross-cutting conventions used across multiple workflows to keep contributions consistent.

Why does my pull request workflow need cross-skill conventions for the Agent Platform?▼

Cross-skill conventions are needed because this skill provides a central source of project standards, including Jira site references, branch naming rules, and architecture overview, that other skills and workflows rely on to maintain consistency across the Agent Platform codebase.