src-app-chat-project-specific

Codify recurring project workflows into reusable decision checklists with examples and anti-patterns.

171|10|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/fmflurry/settings-opencode --skill src-app-chat-project-specific
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: src-app-chat-project-specific
Source: https://github.com/fmflurry/settings-opencode/tree/main/.claude/skills/src-app-chat-project-specific
Command: npx skills add https://github.com/fmflurry/settings-opencode --skill src-app-chat-project-specific

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this pattern when handling recurring project specific workflows.

Core Features & Use Cases

  • Identify recurring project conventions applied during the session.
  • Translate each convention into a simple decision checklist.
  • Show one concrete example from this session.
  • List anti-patterns that should be rejected in future work.

Quick Start

Draft a project-convention checklist for a new initiative using this pattern.

Frequently Asked Questions about src-app-chat-project-specific

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

FAQPage Schema
How do I standardize recurring project workflows across multiple sessions?

Standardize recurring project workflows by codifying team conventions into a reusable pattern. This approach captures governance, checklists, and decision criteria to ensure consistency across multi-project environments and safe handoffs.

What is the best way to translate project conventions into a decision checklist?

Translate project conventions into a decision checklist by identifying recurring rules applied during sessions. You then draft explicit criteria, list anti-patterns to reject, and show one concrete example to guide future work.

How do I prevent anti-patterns from recurring in project management governance?

Prevent recurring anti-patterns in project management governance by explicitly listing rejected practices within a standardized pattern. This establishes clear boundaries and decision criteria for safe collaboration across future initiatives.

Does this project workflow pattern apply to multi-project environments with repeated governance rules?

Yes, this pattern explicitly applies to multi-project environments where teams repeat similar governance, checklists, and decision criteria across different sessions and handoffs.

What do I need to draft a project-convention checklist for a new initiative?

To draft a project-convention checklist for a new initiative, you need explicit frontmatter metadata, example-driven guidance, and decision checklists. This enables repeatable application and safe collaboration.