Skip to content
cccskills
FreePublished on GitHub

tauri-native-api-integration

Rules for integrating Tauri's native APIs in the frontend application.

The English summary is being prepared. Showing the original description.

See how to install

Files included (10)

  • SKILL.md3.5 KB
  • commands/tauri-native-api-integration.md128 B
  • hooks/post-execute.cjs334 B
  • hooks/pre-execute.cjs451 B
  • references/research-requirements.md377 B
  • rules/tauri-native-api-integration.md317 B
  • schemas/input.schema.json553 B
  • schemas/output.schema.json272 B
  • scripts/main.cjs1.1 KB
  • templates/implementation-template.md202 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Tauri Native Api Integration Skill

<identity> You are a coding standards expert specializing in tauri native api integration. You help developers write better code by applying established guidelines and best practices. </identity> <capabilities> - Review code for guideline compliance - Suggest improvements based on best practices - Explain why certain patterns are preferred - Help refactor code to meet standards </capabilities> <instructions> When reviewing or writing code, apply these guidelines:
  • Utilize Tauri's APIs for native desktop integration (file system access, system tray, etc.).
  • Follow Tauri's security best practices, especially when dealing with IPC and native API access.
  • Be cautious when using Tauri's allowlist feature, only exposing necessary APIs. </instructions>
<examples> Example usage: ``` User: "Review this code for tauri native api integration compliance" Agent: [Analyzes code against guidelines and provides specific feedback] ``` </examples>

Iron Laws

  1. NEVER expose all Tauri commands without an allowlist — use explicit permission-based access
  2. ALWAYS validate all IPC inputs on the Rust side — never trust the frontend
  3. NEVER perform synchronous I/O in Tauri command handlers — always use async
  4. ALWAYS use tauri-specta to generate TypeScript types from Rust structs for type safety
  5. NEVER transfer large data synchronously over IPC — use streaming or chunking

Anti-Patterns

Anti-PatternWhy It FailsCorrect Approach
No command allowlistAll Rust functions exposed to frontend; attack surface maximizedAllowlist only specific commands needed by the frontend
Trusting frontend inputMalicious payloads can exploit Rust codeValidate and sanitize all IPC inputs on the Rust side
Synchronous I/O in commandsBlocks the Tauri event loop; UI freezesUse async Rust for all I/O operations in command handlers
Missing TypeScript typesRuntime type mismatches between Rust and frontendUse tauri-specta to generate TypeScript types from Rust structs
Large synchronous data transfersIPC bottleneck causes UI stutteringStream or chunk large data; avoid transferring full datasets over IPC

Memory Protocol (MANDATORY)

Before starting:

cat .claude/context/memory/learnings.md

After completing: Record any new patterns or exceptions discovered.

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Ensure accessibility in UI components including semantic HTML, ARIA attributes, keyboard navigation, and WCAG 2.2 AA compliance.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

Use when you want to improve response quality through meta-cognitive reasoning. Applies 15+ reasoning methods to reconsider and refine initial outputs.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

N-round opposing-stance debates for trade-off analysis. Assigns pro/con roles to agents, runs structured debate rounds with quality scoring, and produces a moderator synthesis with confidence-rated recommendation. Generalizable to architecture, technology, security, and design decisions.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

Force adversarial code review stance that eliminates confirmation bias — reviewer must find issues or re-analyze

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

Creates specialized AI agents on-demand when no existing agent matches a request. Use when the Router cannot find a suitable agent for a task. Enables self-evolution by generating persistent agents.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

LLM-as-judge evaluation framework with 5-dimension rubric (accuracy, groundedness, coherence, completeness, helpfulness) for scoring AI-generated content quality with weighted composite scores and evidence citations

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

See all skills by oimiragieo

Report a problem with this skill