product

Single source of truth for Generacja Innowacja Foundation product work. This repo gathers technical documentation, task definitions, Claude configuration, and operational automations for our products in one place — so anyone (humans or agents) can pick up context without digging across systems.

What lives here

• Technical docs — per-product front-end standards, stack expectations, and project-structure rules (the CLAUDE.md files at the root of each product directory).
• Task & epic specs — markdown tickets organized by product, epic, and cycle/iteration. Used as input for development and for AI-assisted task generation.
• Task templates — TASK_TEMPLATE.md and INSTRUCTIONS.md files defining how new tasks should be authored and what they must reference.
• Claude config & automations — conventions and instructions that drive Claude Code / Claude Agent SDK workflows on top of this repo (task generation, PR scoping, ticket review).

Products

Asystent.NGO

NGO operations assistant. Tasks are organized by iteration under epics/<epic>/cycle-<n>/

• CLAUDE.md — front-end standards, stack, and meta rules for task generation.
• INSTRUCTIONS.md — rules for generating Asystent.NGO tasks (Athena components, scope of styling decisions, file paths).
• PROMPT_TEMPLATE.md — prompt scaffold used when asking Claude to create a task.
• TASK_TEMPLATE.md — required structure for every new task.
• epics/ — task specs grouped by epic and cycle.

myPolitics

Political quiz / civic-engagement product, currently being re-implemented on the new stack. Tasks are organized by epic and development cycle under epics/<epic>/cycle-<n>/.

• CLAUDE.md — front-end standards, stack, and meta rules for task generation.
• INSTRUCTIONS.md — rules for generating myPolitics tasks (Athena components, scope of styling decisions, file paths).
• PROMPT_TEMPLATE.md — prompt scaffold used when asking Claude to create a task.
• TASK_TEMPLATE.md — required structure for every new task.
• epics/ — task specs grouped by epic (home-page, layout, quiz, survey) and cycle.

Conventions

• One product per top-level directory. Each product owns its own CLAUDE.md, templates, and task tree.
• Tasks are markdown. Path encodes scope: epics/<epic>/cycle-<n>/<task-name>.md.
• Every task references the canonical standards in its product's CLAUDE.md and links back to the relevant gi-tech-standards docs.
• New products should be added as a sibling top-level directory, with their own CLAUDE.md and TASK_TEMPLATE.md before any tasks are created.

How Claude is used

The per-product CLAUDE.md files act as machine-readable context for Claude Code / agent workflows. Typical use cases:

• Generating new task tickets from a design link or legacy-code reference, using TASK_TEMPLATE.md + INSTRUCTIONS.md as the contract.
• Reviewing PRs against the documented stack and structure rules.
• Scaffolding new repos from the Vite Project Boilerplate.

Adding a new task

1. Pick the product directory.
2. Follow that product's INSTRUCTIONS.md (if present) and TASK_TEMPLATE.md.
3. Place the file at the path required by the product's convention (see above).
4. Reference the relevant section of the product's CLAUDE.md and any external standards.