@thiagodiogo/pscode 1.0.0 → 1.0.1

package/pscode/content/dixi/kit/react/.editorconfig

@@ -0,0 +1,20 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.{ts,tsx,js,jsx}]
+indent_style = space
+indent_size = 2
+charset = utf-8
+
+[*.{css,scss}]
+indent_style = space
+indent_size = 2
+
+[*.{json,yml,yaml,md}]
+indent_style = space
+indent_size = 2

package/pscode/content/dixi/kit/react/.github/workflows/ci-react.yml

@@ -0,0 +1,80 @@
+name: CI React
+
+on:
+  push:
+    branches: [main, develop]
+  pull_request:
+    branches: [main, develop]
+
+jobs:
+  typecheck:
+    name: Typecheck
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: npm
+      - run: npm ci
+      - name: Type check
+        run: npx tsc --noEmit
+
+  lint:
+    name: Lint
+    runs-on: ubuntu-latest
+    needs: typecheck
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: npm
+      - run: npm ci
+      - name: Lint
+        run: npm run lint
+
+  test:
+    name: Test
+    runs-on: ubuntu-latest
+    needs: typecheck
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: npm
+      - run: npm ci
+      - name: Run tests
+        run: npm test
+
+  build:
+    name: Build
+    runs-on: ubuntu-latest
+    needs: [lint, test]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: npm
+      - run: npm ci
+      - name: Build
+        run: npm run build
+
+  e2e:
+    name: E2E
+    runs-on: ubuntu-latest
+    needs: build
+    if: ${{ hashFiles('playwright.config.ts') != '' }}
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: npm
+      - run: npm ci
+      - name: Install Playwright browsers
+        run: npx playwright install --with-deps
+      - name: Run E2E tests
+        run: npx playwright test

package/pscode/content/dixi/kit/react/.husky/commit-msg

@@ -0,0 +1,2 @@
+#!/usr/bin/env sh
+npx --no-install commitlint --edit "$1"

package/pscode/content/dixi/kit/react/.husky/pre-commit

@@ -0,0 +1,2 @@
+#!/usr/bin/env sh
+npx --no-install lint-staged

package/pscode/content/dixi/kit/react/lint-staged.config.mjs

@@ -0,0 +1,4 @@
+export default {
+  '*.{ts,tsx}': ['eslint --fix', 'prettier --write'],
+  '*.{css,scss,md,json}': ['prettier --write'],
+};

package/pscode/content/dixi/kit/shared/.commitlintrc.yml

@@ -0,0 +1,15 @@
+extends:
+  - '@commitlint/config-conventional'
+
+plugins:
+  - commitlint-plugin-jira-rules
+
+rules:
+  subject-case:
+    - 2
+    - always
+    - lower-case
+  jira-task-id-max-length:
+    - 1
+    - always
+    - 120

package/pscode/content/dixi/kit/shared/.github/pull_request_template.md

@@ -0,0 +1,24 @@
+## O que muda
+
+<!-- Descreva o que esta PR adiciona, modifica ou remove. -->
+
+## Por que (contexto + ticket)
+
+<!-- Explique a motivação da mudança. Inclua o ticket JIRA no formato: Refs: PROJ-123 -->
+
+Refs:
+
+## Como testar
+
+<!-- Passo a passo para validar a mudança localmente ou em ambiente de teste. -->
+
+1.
+2.
+3.
+
+## Checklist
+
+- [ ] Testes passando (`pnpm test` / `mvn test`)
+- [ ] Sem TODO pendente no código
+- [ ] CHANGELOG / changeset atualizado (se aplicável)
+- [ ] Título da PR em formato conventional commit (`feat(scope): descrição [PROJ-123]`)

package/schemas/pstld-workflow/schema.yaml

@@ -0,0 +1,67 @@
+name: pstld-workflow
+version: 1
+description: Dixi workflow - rfc → design → tasks
+artifacts:
+  - id: rfc
+    generates: rfc.md
+    description: Request for Comments document defining the problem and proposed solution
+    template: rfc.md
+    instruction: |
+      Create the RFC document that establishes WHAT needs to be built and WHY.
+
+      Sections:
+      - **Context**: Background, current state, and constraints that motivate this change
+      - **Problem**: Clear statement of the problem being solved
+      - **Proposed Solution**: Description of the solution approach at a conceptual level
+      - **Alternatives Considered**: Other approaches evaluated and why they were rejected
+      - **Architectural Impact**: Effects on existing architecture, dependencies, or interfaces
+      - **Acceptance Criteria**: Verifiable conditions that define when this RFC is satisfied
+
+      Keep the RFC focused on the WHAT and WHY — leave implementation details for design.md.
+      Acceptance Criteria should be specific enough to derive test cases.
+    requires: []
+
+  - id: design
+    generates: design.md
+    description: Technical design document with implementation approach and decisions
+    template: design.md
+    instruction: |
+      Create the design document that explains HOW to implement the RFC.
+
+      Sections:
+      - **Affected Components**: List of modules, services, or layers touched by this change
+      - **Interface Contracts**: APIs, function signatures, data shapes, or protocol changes
+      - **Test Plan**: What to test, at which layer (unit/integration/e2e), and key scenarios
+      - **Security Considerations**: Authentication, authorization, input validation, data exposure risks
+
+      Reference the RFC for motivation and acceptance criteria.
+      Focus on concrete technical decisions and their rationale.
+    requires:
+      - rfc
+
+  - id: tasks
+    generates: tasks.md
+    description: Implementation checklist derived from RFC and design
+    template: tasks.md
+    instruction: |
+      Create the task list that breaks down the implementation work.
+
+      Guidelines:
+      - Group related tasks under ## numbered headings
+      - Each task MUST be a checkbox: `- [ ] X.Y Task description`
+      - Tasks should be small enough to complete in one session
+      - Order tasks by dependency (what must be done first?)
+      - End with a Definition of Done section
+
+      Reference the RFC acceptance criteria and design decisions.
+      Each task should be verifiable — you know when it's done.
+    requires:
+      - rfc
+      - design
+
+apply:
+  requires: [tasks]
+  tracks: tasks.md
+  instruction: |
+    Read context files, work through pending tasks, mark complete as you go.
+    Pause if you hit blockers or need clarification.

package/schemas/pstld-workflow/templates/design.md

@@ -0,0 +1,15 @@
+## Affected Components
+
+<!-- List of modules, services, or layers touched by this change -->
+
+## Interface Contracts
+
+<!-- APIs, function signatures, data shapes, or protocol changes -->
+
+## Test Plan
+
+<!-- What to test, at which layer (unit/integration/e2e), and key scenarios -->
+
+## Security Considerations
+
+<!-- Authentication, authorization, input validation, data exposure risks -->

package/schemas/pstld-workflow/templates/rfc.md

@@ -0,0 +1,26 @@
+## Context
+
+<!-- Background, current state, and constraints that motivate this change -->
+
+## Problem
+
+<!-- Clear statement of the problem being solved -->
+
+## Proposed Solution
+
+<!-- Description of the solution approach at a conceptual level -->
+
+## Alternatives Considered
+
+<!-- Other approaches evaluated and why they were rejected -->
+
+## Architectural Impact
+
+<!-- Effects on existing architecture, dependencies, or interfaces -->
+
+## Acceptance Criteria
+
+<!-- Verifiable conditions that define when this RFC is satisfied -->
+
+- [ ] <!-- Criterion 1 -->
+- [ ] <!-- Criterion 2 -->

package/schemas/pstld-workflow/templates/tasks.md

@@ -0,0 +1,15 @@
+## 1. <!-- Task Group Name -->
+
+- [ ] 1.1 <!-- Task description -->
+- [ ] 1.2 <!-- Task description -->
+
+## 2. <!-- Task Group Name -->
+
+- [ ] 2.1 <!-- Task description -->
+- [ ] 2.2 <!-- Task description -->
+
+## Definition of Done
+
+- [ ] All acceptance criteria from the RFC are met
+- [ ] Test plan from design is executed
+- [ ] No regressions in existing functionality