playbooks

home / skills / oimiragieo / agent-studio / todo-app-general-rules

todo-app-general-rules skill

/.claude/skills/_archive/dead/todo-app-general-rules

This skill helps enforce todo app general rules by reviewing code for guidelines, suggesting improvements, and explaining best practices across the project.

npx playbooks add skill oimiragieo/agent-studio --skill todo-app-general-rules

Review the files below or copy the command above to add this skill to your agents.

Files (3)
SKILL.md
1.5 KB
---
name: todo-app-general-rules
description: General rules for the entire Todo web application project. Encompasses specifications and guidelines applicable across all files.
version: 1.0.0
model: sonnet
invoked_by: both
user_invocable: true
tools: [Read, Write, Edit]
globs: /**/*.*
best_practices:
  - Follow the guidelines consistently
  - Apply rules during code review
  - Use as reference when writing new code
error_handling: graceful
streaming: supported
---

# Todo App General Rules Skill

<identity>
You are a coding standards expert specializing in todo app general rules.
You help developers write better code by applying established guidelines and best practices.
</identity>

<capabilities>
- Review code for guideline compliance
- Suggest improvements based on best practices
- Explain why certain patterns are preferred
- Help refactor code to meet standards
</capabilities>

<instructions>
When reviewing or writing code, apply these guidelines:

- Use the project specifications and guidelines to build the Todo app.
- Todo is a web app that allows you to manage your todos.
  </instructions>

<examples>
Example usage:
```
User: "Review this code for todo app general rules compliance"
Agent: [Analyzes code against guidelines and provides specific feedback]
```
</examples>

## Memory Protocol (MANDATORY)

**Before starting:**

```bash
cat .claude/context/memory/learnings.md
```

**After completing:** Record any new patterns or exceptions discovered.

> ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

Overview

This skill defines general rules and coding standards for a Todo web application project. It provides cross-file guidelines, consistent conventions, and practical checks to keep the codebase maintainable and predictable. Use it to align implementations with agreed project-level conventions.

How this skill works

The skill inspects code and project structure for adherence to the shared Todo app rules: naming, component responsibilities, state management boundaries, file organization, and common patterns. It highlights violations, explains why a pattern is problematic, and proposes concrete fixes or refactors. The skill can also suggest test and documentation additions to cover the changes.

When to use it

  • When adding new features that touch multiple modules (UI, store, API)
  • During code reviews to enforce project-wide conventions
  • When refactoring to simplify cross-cutting concerns like state or routing
  • Before merging PRs that change app behavior or public interfaces
  • When onboarding contributors to ensure consistent style and architecture

Best practices

  • Keep components focused: UI components accept props and emit events; business logic lives in services or stores
  • Use a single source of truth for todo state; avoid duplicate local and global states for the same data
  • Prefer clear, consistent naming for actions, mutations, and selectors (e.g., addTodo, removeTodo, getTodos)
  • Organize files by feature (feature folder per todo domain) rather than by type for easier navigation
  • Write small, pure helper functions and unit tests for them; mock external dependencies in component tests

Example use cases

  • Review a pull request that introduces optimistic UI updates and ensure rollback and error handling are covered
  • Assess a refactor that moves todo filtering from components into selectors to improve reusability
  • Validate a new persistence layer (localStorage or API) to ensure migration and compatibility rules are met
  • Audit naming and file placement when a contributor adds a new Todo subfeature to maintain consistency

FAQ

Does the skill enforce a specific framework or library?

No. The rules are framework-agnostic; they focus on structure, separation of concerns, naming, and state consistency. Framework-specific suggestions can be provided when requested.

How does this skill handle exceptions to the rules?

It documents proposed exceptions, explains trade-offs, and recommends minimal, time-limited deviations with follow-up plans to reduce technical debt.