talaris-project-toolkit

Use when: planning, executing, or reviewing delivery work using Kanban boards, WIP limits, pull-based flow, and continuous improvement practices.

Use when: designing, building, or reviewing UI to meet WCAG 2.2 Level AA accessibility requirements across forms, navigation, content, and interactions.

Use when: implementing login, session controls, role-based access control, and permissions across system, programme, project, and module contexts.

Use when: implementing immediate backend persistence from frontend edits without full form submission, including validation and failure handling.

Use when: designing or refactoring feature architecture in CodeIgniter for maintainability, separation of concerns, and module consistency.

Use when: building programme/project dashboards, drill-down detail views, and cross-module reports with traceable source links.

Use when: preparing deployment for local development, shared hosting, and VPS targets with environment-safe configuration.

Use when: writing or updating product and technical documentation in Markdown for a Jekyll site with Bootstrap-based theme.

Use when: implementing scheduled report emails and notification delivery with configurable frequency and recipient targeting.

Use when: building UI components with Bootstrap 5 and Bootstrap Icons while maintaining consistency and accessibility.

Use when: applying GPL licensing requirements, legal headers, attribution, and open-source release hygiene in repository files.

Use when: implementing localization, browser language detection, fallback to English, and user language override via cookie.

Use when: designing or updating pages with mobile-first layout, responsive behavior, and touch-friendly interactions.

Use when: defining or consuming internal APIs that allow modules to read and update each other safely.

Use when: designing or implementing pluggable modules with shared structure, conventions, and lifecycle within the toolkit application.

Use when: designing MySQL/MariaDB schema, migrations, and concurrency controls such as checkout/locking for records or modules.

Use when: implementing PHP backend features in CodeIgniter 4, including controllers, models, validation, routing, and framework conventions.

Use when: modeling programme/project workflows and implementing RAID-based modules (risks, assumptions, issues, dependencies).

Use when: writing or reviewing PHP to enforce PSR-12 style, readability, and maintainable code quality.

Use when: adding security controls, hardening data handling, and implementing audit logs for all changes with actor and timestamp.

Use when: creating or updating test coverage across unit, integration, and system/end-to-end levels for application features and modules.

Use when: implementing admin-configurable branding such as logo, heading/body fonts, and color scheme across the application.