CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

ainativedev/aidevcon-2026-nyc

AI Native DevCon 2026 New York — practical agent skills grounded in conference talks

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

application-template.mdskills/talk-gavrilescu-factory-architecture/references/

Architecture change review

This worksheet is a recommended application of Gavrilescu's loop. It does not claim to implement Groma.

Review scope

Task intent and product behavior: What should the feature do, and which user flow demonstrates it?

Baseline and result: Identify the actual revisions or snapshots being compared. Mark whether the map was initialized before this work; do not invent earlier architecture history.

Coverage: List relevant languages, frameworks and components. Note known scanner limitations or areas that were not inspected.

Structural evidence and interpretation

Component or relationshipObserved sourceMeaning or flowConfidence
Fill with an actual entityFile, symbol or inspected evidenceCurated explanationVerified, inferred or unknown

Keep deterministic facts separate from agent-generated labels and flow descriptions. Include a small set of important paths that were checked against source. For every missing edge, distinguish “not observed” from “confirmed absent.”

Changes to review

Describe components added, removed or modified, changed dependencies and which changes are expected from the task. Identify duplication, bypasses around shared services and code apparently disconnected from product behavior.

Cumulative concern: Explain whether this change continues a pattern visible across several features. Include the comparison period rather than implying one pull request proves system-wide drift.

Decision and verification

For each concern, state evidence, architectural consequence, proposed correction and the behavior or source inspection that would validate it. Record any focused code review needed where the map is insufficient.

Product check: Describe how the final application was or should be exercised. Do not mark planned checks as completed.

Next baseline: State how reviewed names, groupings and stable component identity will be maintained. End with accepted changes, unresolved uncertainty and the next review trigger appropriate to this project.

skills

talk-gavrilescu-factory-architecture

tile.json