CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

app-reference-architecture

Molde arquitetural completo para apps novos que precisam de login, pagamento, push, landing page, web app e APK Android a partir do mesmo codigo-fonte (Next.js + Tauri v2), deploy via Docker/Coolify e build/publicacao de APK via GitHub Actions. Extraido por engenharia reversa de 3 apps reais em producao do autor (gastos-app, memrapp, VisaLab) para que todo app novo nasca na mesma estrutura testada, sem reinventar auth dual, build estatico Tauri, multi-pagamento (Stripe + Google Play IAP + Pix) ou push multi-canal a cada projeto. Trigger em: "novo app", "app do zero", "greenfield mobile", "Next.js + Tauri", "APK do zero", "arquitetura de referencia", "auth dual web e app", "gerar APK a partir do Next.js", "template de SaaS", "monetizar app mobile", "Google Play IAP", "assinatura Stripe e Play Store", "mesma estrutura dos outros apps", "boilerplate de app", "starter kit mobile+web".

68

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized architecture-decision body: dense, concrete guidance (exact rules, named tools, a decision table with defaults, explicit anti-patterns) with a clear 7-step workflow and one genuine validation checkpoint with error recovery. The main costs are structural repetition of the skill-boundary meta-explanation, scattered repeated pointers to the single external guide, and the absence of any reference code inside the body itself.

Suggestions

Consolidate the 'esta skill decide a arquitetura, as skills de domínio implementam' boundary — currently restated in Governanca, Quando Nao Usar, Responsabilidade 7, Handoff, and Integracao — into one canonical statement and drop the repetitions.

Gather the 8+ scattered pointers to docs/skill-guides/app-reference-architecture.md into a single 'Guia de referência' section mapping each topic (Auth, Build Tauri, Pagamentos, Push, Docker/CI-CD, Guia de Decisão) to its guide section, citing it once per Responsabilidade at most.

Add a small inline skeleton for the highest-risk artifact (the Tauri build swap/restore script's finally block) so the core pattern is executable from the body, since the referenced guide file is not part of this skill bundle.

DimensionReasoningScore

Conciseness

Dense decision content throughout with zero concept-explanation padding — it never explains what Next.js, Docker, webhooks, or VAPID are, and assumes Claude's competence. Noticeable structural repetition keeps it from anchor 5: the 'esta skill decide, as outras implementam' boundary is restated ~5 times (Governanca, Quando Nao Usar, Responsabilidade 7, Handoff, Integracao) and the guide path is pointed to 8+ times. Clearly above anchor 3, which would require unnecessary explanation rather than intentional-but-trimmable signposting.

4 / 5

Actionability

Highly concrete named guidance: 'renomeia, nunca deleta... restaura tudo no finally', a single Subscription table with the exact status values (active/trialing/grace_period/canceled/past_due/account_hold), 'cron de reconciliação diário' for RTDN, r0adkll/upload-google-play@v1, and exact output files (next.config.tauri.mjs, scripts/build-tauri.js, .github/workflows/android-release.yml). Not anchor 5: the actual reference code for every piece is deferred to the external guide, so the body itself has minor gaps an implementer must leave to fetch.

4 / 5

Workflow Clarity

Clear 7-step sequence (classify app type → auth → Tauri build → payment → push → Docker/CI → register decision + handoff) with one explicit validation checkpoint and error-recovery loop ('Checkpoint: rodar o build Tauri de verdade... Se o build falhar, checar primeiro se o finally rodou') plus a completion checklist (Evidencia de Conclusao). Anchor 4 rather than 5 because validation exists only for the Tauri build step; the other decisions (e.g., payment webhook, push delivery) lack equivalent checkpoints.

4 / 5

Progressive Disclosure

Good one-level-deep reference pattern — each section names exactly which guide section holds the detail ('Ver seção "3. Pagamentos" no guia para schema completo, webhook idempotente'). Not anchor 5: the referenced docs/skill-guides/app-reference-architecture.md is not present in this skill bundle (no references/ directory, so the pointer is unverifiable), the pointer is repeated 8+ times instead of consolidated, and sibling references (GLOBAL.md, policies/*.md) are likewise external. Above anchor 3, since references are clearly signaled with their content described rather than buried.

4 / 5

Total

16

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it explicitly states what the skill covers with concrete stack specifics (Next.js + Tauri v2, Stripe + Google Play IAP + Pix, Docker/Coolify, GitHub Actions) and provides an explicit, comprehensive trigger list with natural synonym variation. The only weakness is that it describes the artifact ('Molde arquitetural completo') rather than the actions the skill performs, leaving the decide/scaffold behavior implicit.

DimensionReasoningScore

Specificity

Enumerates concrete, specific coverage — 'login, pagamento, push, landing page, web app e APK Android a partir do mesmo codigo-fonte (Next.js + Tauri v2)', 'deploy via Docker/Coolify', 'build/publicacao de APK via GitHub Actions', 'auth dual, build estatico Tauri, multi-pagamento (Stripe + Google Play IAP + Pix)'. It describes what the mold IS rather than actions the skill PERFORMS (decide/scaffold is only implied), so it fits anchor 4 (several specific items, minor gaps) rather than the verb-driven 'multiple specific concrete actions' of anchor 5; clearly above anchor 3, which would cover only 1-2 concrete actions.

4 / 5

Completeness

Explicitly answers both what ('Molde arquitetural completo para apps novos que precisam de login, pagamento, push... a partir do mesmo codigo-fonte') and when ('Trigger em: [15 concrete phrases]') — exactly the anchor-5 pattern of an explicit trigger clause with concrete phrases. Not 4, because the when-guidance is not merely present-but-improvable; it is fully explicit.

5 / 5

Trigger Term Quality

The explicit 'Trigger em:' list gives 15 natural phrases with genuine synonym variation — 'novo app', 'app do zero', 'greenfield mobile', 'boilerplate de app', 'starter kit mobile+web', 'template de SaaS', 'gerar APK a partir do Next.js'. This matches the anchor-5 pattern of comprehensive natural-term coverage including synonyms (stack names like 'Next.js + Tauri' play the file-extension role here); anchor 4 would require noticeable missing terms.

5 / 5

Distinctiveness Conflict Risk

Clear niche (monetized web+APK apps on Next.js + Tauri) with distinct triggers ('Next.js + Tauri', 'auth dual web e app', 'Google Play IAP', 'assinatura Stripe e Play Store') that adjacent skills (generic backend, Tauri-only, deploy-only) would not claim. Third-person voice throughout, so no voice penalty applies; minimal conflict risk per anchor 5.

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/60-app-reference-architecture/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.