busya/ss-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

rename ss-tools to superset-tools across the entire project

Browse Source 
- Replace all occurrences of 'ss-tools' with 'superset-tools' in 104 files
- Rename git bundle file ss-tools.bundle → superset-tools.bundle
- Update .gitignore pattern accordingly
- Preserve variable names (hasSsTools etc.) and code identifiers
This commit is contained in:
busya
2026-06-16 11:15:19 +03:00
parent d75db60343
commit ec6421de35
129 changed files with 467 additions and 467 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
.opencode/agents/speckit.md
View File

@@ -1,5 +1,5 @@
---
description: Speckit Workflow Specialist — runs the full feature lifecycle from specification through planning, task decomposition, and implementation for Python/Svelte ss-tools features.
description: Speckit Workflow Specialist — runs the full feature lifecycle from specification through planning, task decomposition, and implementation for Python/Svelte superset-tools features.
mode: all
model: deepseek/deepseek-v4-pro
temperature: 0.2
@@ -30,7 +30,7 @@ See `semantics-core` §VI for the canonical tool reference. For planning:
## Core Mandate
- Own the full feature lifecycle: `/speckit.specify` → `/speckit.clarify` → `/speckit.plan` → `/speckit.tasks` → `/speckit.implement`.
- Every output artifact must be traceable to semantic contracts, ADR guardrails, and the ss-tools repository reality (Python backend + Svelte frontend).
- Every output artifact must be traceable to semantic contracts, ADR guardrails, and the superset-tools repository reality (Python backend + Svelte frontend).
- Never skip a phase. Never proceed with unresolved `[NEEDS CLARIFICATION]` markers.
## Required Workflow
@@ -62,7 +62,7 @@ See `semantics-core` §VI for the canonical tool reference. For planning:
### 3. Planning (`/speckit.plan`)
1. Run `.specify/scripts/bash/setup-plan.sh --json` to initialize `plan.md`.
2. Load all canonical context: `README.md`, `requirements.txt`, `frontend/package.json`, all ADRs, constitution, skill files, plan template.
3. Fill `Technical Context` with real ss-tools reality: Python 3.9+ / FastAPI / SQLAlchemy backend, SvelteKit 5 / Tailwind frontend, Docker deployment.
3. Fill `Technical Context` with real superset-tools reality: Python 3.9+ / FastAPI / SQLAlchemy backend, SvelteKit 5 / Tailwind frontend, Docker deployment.
4. Fill `Constitution Check` — ERROR if blocking conflict found.
5. Phase 0 — write `research.md`: resolve all material unknowns (API design, component placement, data model, async patterns, migration strategy, ADR continuity). Each item must include Decision, Rationale, Alternatives Considered, Impact.
6. Phase 1 — write `data-model.md`, `contracts/modules.md`, `quickstart.md`.