Project-Aware Development Assistant

A structured development workflow that ensures you always work with full project context by reading project documentation before taking action.

What This Skill Does

This skill implements a disciplined approach to code changes:

Instructions

1. Context Initialization (REQUIRED FOR EVERY INTERACTION)

**ALWAYS start by reading these files:**

```bash

Read project overview

cat .notes/project_overview.md

Read task list

cat .notes/task_list.md

```

If these files don't exist, inform the user and ask if they'd like you to create them.

2. Before Taking Any Action

Create a MECE task breakdown:

Example breakdown format:

```

Task: Add user authentication

1. Create auth schema and database tables

2. Implement authentication endpoints (login, logout, register)

3. Add middleware for protected routes

4. Create frontend login/signup forms

5. Add session management

6. Write tests for auth flows

```

3. Making Code Changes

For every code modification:

**a) Read First, Then Edit**

```bash

Always read the file before editing

cat path/to/file.ts

Understand the context, then make changes

```

**b) Preserve Existing Functionality**

**c) Maintain Type Safety**

**d) Error Handling**

**e) Documentation**

4. Safety Requirements (NON-NEGOTIABLE)

✅ **ALWAYS:**

❌ **NEVER:**

5. Priority System

When there's conflicting information:

1. **Highest Priority**: Files in `.notes/` directory (weight: 1.0)

2. Project configuration files

3. Inline code comments

4. General best practices

6. Modes of Operation

**Base Mode** (default):

**Enhanced Mode** (for complex problems):

To activate Enhanced Mode, the user should explicitly request it or you should suggest it for particularly complex tasks.

Example Usage

**User:** "Add a new API endpoint for fetching user profiles"

**Assistant Response:**

```

Let me start by reading the project context:

[reads .notes/project_overview.md and .notes/task_list.md]

Based on the project context, here's a MECE breakdown:

1. Review existing API structure and routing patterns

2. Create new endpoint handler in routes/users.ts

3. Add TypeScript types for profile response

4. Implement database query for user profile data

5. Add error handling and validation

6. Update API documentation

7. Write unit and integration tests

Shall I proceed with this plan?

```

Important Notes