full-stack-skills/tauri-skills / skills/tauri-app-planning
tauri-app-planning
VerifiedComprehensive project planning, requirements analysis, and architectural orchestration for Tauri 2.0 applications.
| File | Kind | Size |
|---|---|---|
| LICENSE.txt | markdown | 11.1 KB |
| SKILL.md | skill md | 1.4 KB |
| agents/openai.yaml | config | 322 B |
| examples/architecture-patterns.md | markdown | 2.7 KB |
| examples/usage.md | markdown | 966 B |
| templates/project-plan.md | markdown | 1.4 KB |
| templates/todo-list.md | markdown | 825 B |
templates/project-plan.md
View on GitHub# Technical Implementation Plan: [Project Name]
## 1. Overview
**Goal**: [Brief description of the app]
**Platforms**: [Desktop (Win/Mac/Linux), Mobile (iOS/Android)]
## 2. Skills & Plugins Strategy
| Capability | Tauri Plugin | Usage |
| :--- | :--- | :--- |
| File Storage | `tauri-plugin-fs` | Reading/Writing local files |
| Database | `tauri-plugin-sql` | Local SQLite data |
| Networking | `tauri-plugin-http` | API requests |
| ... | ... | ... |
## 3. Architecture Design
### Frontend
- **Framework**: [Vue/React/Svelte]
- **State Management**: [Pinia/Redux/Context]
- **Router**: [Vue Router/React Router]
### Backend (Rust)
- **State**: `AppState` struct holding [components].
- **Commands**:
- `get_data`
- `save_settings`
- ...
### Orchestration
- **Windows**:
- `main`: Primary interface.
- `[other]`: [Purpose]
- **Events**:
- `[event-name]`: [Trigger] -> [Action]
## 4. Security Scope (Capabilities)
**Identifier**: `default`
**Windows**: `main`
**Permissions**:
- `core:default`
- `fs:allow-read-text-file` (Scope: `$APP_DATA/*`)
- ...
## 5. Implementation Roadmap
1. [ ] **Setup**: Initialize project and Git.
2. [ ] **Core**: Implement Rust State and basic Commands.
3. [ ] **UI**: Build the main layout.
4. [ ] **Feature A**: Implement [Feature A].
5. [ ] **Feature B**: Implement [Feature B].
6. [ ] **Release**: Build and Sign.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |