presonus-studiolive-mcp: Instructions file for GitHub Copilot

.github/instructions/phase-04-design.instructions.md

presonus-studiolive-mcp phase-04-design.instructions.md is an instructions file for GitHub Copilot from zarfld/presonus-studiolive-mcp. It costs 6,003 tokens per session, scanned A, original, MIT.

Guidance for turning a software architecture into detailed implementation designs. It covers components, classes, interfaces, data models, database schemas, algorithms, and reusable design patterns.

In plain words
What is it for?
Use it to specify component behavior, class structures, interfaces, data storage, algorithms, and design choices for an implementation.
Why use it?
It provides a written design that developers can follow before coding. It also connects detailed decisions to the architecture and requirements they came from.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is zarfld/presonus-studiolive-mcp's own configuration. It tells GitHub Copilot how to work on presonus-studiolive-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything presonus-studiolive-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to zarfld/presonus-studiolive-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/zarfld/presonus-studiolive-mcp/master/.github/instructions/phase-04-design.instructions.md
Clone the repo
git clone --depth 1 https://github.com/zarfld/presonus-studiolive-mcp

Made for: GitHub Copilot.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for presonus-studiolive-mcp phase-04-design.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/phase-04-design/github.svg)](https://agentmods.dev/instructions/zarfld/presonus-studiolive-mcp/phase-04-design)
Your own site
<a href="https://agentmods.dev/instructions/zarfld/presonus-studiolive-mcp/phase-04-design"><img src="https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/phase-04-design/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for presonus-studiolive-mcp phase-04-design.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/zarfld/presonus-studiolive-mcp/phase-04-design"><img src="https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/phase-04-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6,003 This file is loaded in full into every session.
When invoked 6,003 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.06003 $0.06003
Opus 5 $0.03002 $0.03002
Sonnet 5 $0.01201 $0.01201
Haiku 4.5 $0.00600 $0.00600

Measured 12d ago against content hash 1b7815b0f57f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

presonus-studiolive-mcp phase-04-design.instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/instructions/phase-04-design.instructions.md · 988 lines

How it starts

The opening of the file, as written. The whole thing — 988 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Phase 04: Detailed Design

Standards: IEEE 1016-2009 (Software Design Descriptions)
XP Integration: Simple Design, CRC Cards, Design Patterns
DDD Integration: Entity, Value Object, Aggregate, Repository, Factory, Domain Service, Specification

🎯 Phase Objectives

  1. Transform architecture into detailed component designs using DDD tactical patterns
  2. Define class structures, interfaces, and algorithms with Design by Contract
  3. Specify data models and database schemas respecting domain model
  4. Document design patterns and implementation approaches
  5. Create design specifications enabling implementation

📋 Design Documentation Approach

⭐ PRIMARY: Link to Architecture Issues (GitHub Issues)

Design artifacts reference architecture issues created in Phase 03. Detailed designs can be:

  • GitHub Issue comments on architecture component issues (ARC-C)
  • Wiki pages linked from architecture issues
  • Markdown files in 04-design/ with issue references
Linking Design to Architecture Issues

Every design specification MUST reference:

  • Architecture Component Issue: #N (from ARC-C templates)
  • Architecture Decisions: #N (from ADR templates)
  • Requirements: #N (from REQ-F/REQ-NF templates)

Example Design File Header:

# User Authentication Service - Detailed Design

**Architecture Component**: #79 (ARC-C-AUTH: User Authentication Service)
**Architecture Decisions**:
- #78 (ADR-SECU-001: JWT Authentication)
- #80 (ADR-DATA-001: PostgreSQL for User Data)

**Requirements**:
- #45 (REQ-F-AUTH-001: User Login)
- #46 (REQ-NF-SECU-002: Session Security)

---

## Class Diagram
## Sequence Diagrams
## Data Models
Comment on Architecture Issues

Add detailed design as comment on architecture component issue:

Comment on Issue #79 (ARC-C-AUTH):

## Detailed Design

### Class Structure
\`\`\`typescript
class UserService {
  constructor(
    private userRepository: IUserRepository,
    private jwtService: IJwtService,
    private passwordHasher: IPasswordHasher
  ) {}

  async login(credentials: Credentials): Promise<AuthResult> {
    // Implementation details
  }
}
\`\`\`

### Sequence Diagram
[Mermaid diagram or link to diagram]

### Data Model
[Tables, schemas, relationships]

### Design Patterns
- Repository Pattern for data access
- Dependency Injection for testability
- Strategy Pattern for password hashing algorithms

Read the full file on GitHub · 988 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 988 lines · 6,003 tokens per session scan A 1b7815b0f57f

Subscribe to this mod's changes

presonus-studiolive-mcp phase-04-design.instructions.md is an instructions file published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 6,003 tokens to every session, about $0.0300 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other instructions, from other repositories

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,126 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens