getphred/Tasker
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity
Tasker/.junie/guidelines.md
Funky Waddle 3ac2894fd8
Some checks are pending
CI / tasker (8.2) (push) Waiting to run
Details
CI / tasker (8.3) (push) Waiting to run
Details
feat: complete Tasker project implementation, documentation, and examples
2026-02-22 01:14:22 -06:00

2.2 KiB
Raw Blame History

Tasker CLI Tool Manager: Development Guidelines

These guidelines ensure that all development by AI agents remains consistent with the project's standards for quality, maintainability, and architectural purity.

1. Execution Policy (CRITICAL)

  • Sequential Implementation: Milestones defined in MILESTONES.md MUST be implemented one at a time.
  • No Auto-Advance: Do not automatically move to the next milestone. Stop and wait for verification or explicit instruction after completing a milestone.
  • Strict Milestone Completion (Definition of Done - Milestones): A milestone is NOT complete until:
    • The full suite of tests passes.
    • Zero deprecation warnings.
    • Zero errors.
    • Zero failures.
  • Strict Project Completion (Definition of Done - Project): A project is NOT complete until:
    • All milestones are verified as complete
    • The project meets all defined requirements
    • A test run of GitHub workflow has been completed with no errors and no warnings

2. Core Requirements

  • PHP Version: ^8.2
  • Principles:
    • SOLID: Strict adherence to object-oriented design principles.
    • KISS: Prefer simple solutions over clever ones.
    • DRY: Minimize duplication by abstracting common logic.
    • YAGNI: Avoid over-engineering; only implement what is actually required.

3. Coding Style & Architecture

  • Verbose Coding Style: Code must be expressive and self-documenting. Use descriptive variable and method names.
  • Single Responsibility Principle (SRP):
    • Classes: Each class must have one, and only one, reason to change.
    • Methods: Each method should perform a single, well-defined task.
  • Type Safety: Strictly use PHP 8.2+ type hinting for all properties, parameters, and return values.
  • Interoperability: Prioritize PSR compliance (especially PSR-7 for HTTP messages).

4. Documentation & Quality Assurance

  • Well Documented: Every public class and method must have comprehensive PHPDoc blocks.
  • Fully Tested:
    • Aim for high test coverage.
    • Every bug fix must include a regression test.
    • Every new feature must be accompanied by relevant tests.
    • Use PHPUnit for the testing suite.