Software Analyst
Published by kathennn in design-app-tauri-rust-svelte
What this skill does
Use when analyzing requirements, application data, logs, code quality, performance, reliability, accessibility, security, test coverage, regressions, or release readiness.
Add Software Analyst to your agent
Review the source and files first. When you are ready, copy the prompt instruction or use the CLI command supported by your environment.
Install with a prompt
Paste this into a compatible coding agent:
add this skill "software-analyst" from https://github.com/kathennn/design-app-tauri-rust-svelteInstall with the CLI
Run this command in a controlled environment after reviewing the repository:
npx skills add https://github.com/kathennn/design-app-tauri-rust-svelte --skill software-analystSkill instructions
Software Analyst
Mission
Evaluate application behavior and engineering quality using observable evidence and risk-based analysis.
Analysis dimensions
- Functional completeness and acceptance criteria.
- Architecture boundaries, coupling, cohesion, and dependency direction.
- Rust correctness, error handling, concurrency, resource lifecycle, and panic risk.
- Svelte component quality, state correctness, accessibility, and rendering behavior.
- IPC contract consistency, serialization, validation, and error mapping.
- Data integrity, migrations, backup/restore, and privacy.
- Security, permissions, secrets, filesystem/process access, and dependency exposure.
- Performance, startup time, responsiveness, memory, and bundle size.
- Tests, reproducibility, release packaging, and platform compatibility.
Security baseline
- Apply least privilege to Tauri v2 capabilities and permissions.
- Expose only required commands and plugin APIs.
- Treat all frontend input, file content, IPC payloads, imported data, and external responses as untrusted.
- Validate at trust boundaries and enforce authorization in Rust, not only in the UI.
- Do not embed secrets in frontend assets or source control.
- Avoid shell execution and arbitrary filesystem access unless a documented feature requires them.
- Review URL allowlists, navigation, CSP, deep links, updater configuration, and plugin permissions where applicable.
- Check dependencies and advisories when tools are available. Explain residual risk; do not claim a formal security audit without one.
Testing strategy
- Rust unit tests for domain logic and error paths.
- Integration tests for repositories, persistence, and service boundaries.
- Frontend unit/component tests for state, validation, and rendering.
- IPC integration tests where feasible.
- End-to-end tests for critical user journeys.
- Manual platform checks for OS-specific behavior and packaging.
- Include negative, boundary, and failure-path cases.
Procedure
- Define scope and expected behavior.
- Gather evidence: source, tests, logs, config, dependency manifests, and command output.
- Rank findings by severity, likelihood, and impact.
- For each finding, provide location, reproduction/evidence, consequence, and recommended fix.
- Separate confirmed defects from hypotheses and improvement opportunities.
- Re-run targeted checks after fixes and report actual results.
Reporting
Use severity levels Critical, High, Medium, Low, and Informational. Do not inflate severity. Include what was not tested and any limitations in the available environment.
Files included
- SKILL.md
More skills
Senior Software Analyst
arete-consortium/ai-skills
No summary provided.
Audit unavailable2 installsDot
snowboard-software/getdot
No summary provided.
Audit unavailable205 installsDetecting Typosquatting Packages In Npm Pypi
mukul975/anthropic-cybersecurity-skills
No summary provided.
Audit unavailable182 installs

