← all publishers

avizmarlon

@avizmarlon source repo

Report this profile Claim this profile

• 31 skills
• 0 followers
• 11 hours ago last updated

1. ▌
   Observability When To Add · avizmarlon

   Instrumentation is directed, not preventive — add observability only when confirmed pain exists. Follow industry standards (OpenTelemetry, structured logging, performance.now()). Use when implementing metrics, tracing, performance debugging, or asking whether instrumentation is needed.
   0 installs
2. ▌
   Large Payload Completeness · avizmarlon

   Verify large payload fetches are COMPLETE — anti silent-truncation. Cross-check size vs expected, follow all pagination cursors. Use when fetching from paginated APIs, large databases, HAR files, log dumps, transcripts, or any payload >50k chars.
   0 installs
3. ▌
   Excellence No Intermediates · avizmarlon

   No intermediate options in trade-offs — every choice presented must be a path to excellence, never "accept broken state temporarily" or "good enough for now." Use when presenting trade-off decisions, discussing defect fixes, proposing feature scope, debating technical debt, MVP boundaries, and sequencing.
   0 installs
4. ▌
   Permanent Learning Protocol · avizmarlon

   Permanent learning — AI agent proposes learnings from sessions, user approves in chat, integrations saved to auto-loaded files. Triggers on session end or manual /learn command. Use when consolidating discoveries, user says learn/consolidate/document, or end-of-session signals.
   0 installs
5. ▌
   Reactive Integration Design · avizmarlon

   Observe facts, not promises — prefer kernel/runtime event streams (docker events, inotify, K8s watch, fanotify, journald) over application-level webhooks/callbacks. Use when designing reactive integrations to external system events, building event-driven architectures, and avoiding silent integration failures across version upgrades.
   0 installs
6. ▌
   Impact Metrics Gate · avizmarlon

   Measure before building — enforce impact metrics definition before project/feature development. Use when starting projects, defining features, or setting success criteria.
   0 installs
7. ▌
   Ledger Auto Updates · avizmarlon

   Automatic documentation updates at end of substantive sessions. Update CHANGELOG + session-handoff without being asked. Triggers on session-end signals (farewells, wrap-up requests, topic pivots after coherent work, or context limits approaching).
   0 installs
8. ▌
   LLM Model Selection · avizmarlon

   Select the right LLM for a task by consulting benchmarks and real performance data. Use when choosing between models (chatbot, agent, text classification, code generation, etc.), comparing model performance, or validating model availability and pricing.
   0 installs
9. ▌
   Multi Phase Session · avizmarlon

   Manage multi-phase projects using separate sessions per phase instead of compact, with durable handoff files. Use when work spans multiple sessions, phases, handoffs, or when context degradation becomes a concern.
   0 installs
10. ▌
    Secure Secret Input · avizmarlon

    Collect sensitive values from users via secure local prompts, never in chat. Use when asking for API keys, tokens, passwords, or any secret that should remain hidden from logs.
    0 installs
11. ▌
    Agent Runtime Parity · avizmarlon

    Maintain configuration and capability parity across multiple AI agent runtimes (Claude, Codex, Cursor, Gemini, custom agents). Use when syncing rules, skills, MCPs, configs, or credentials across team AI tools, or when debugging drift between agents.
    0 installs
12. ▌
    Compact Instructions · avizmarlon

    Context preservation strategy for multi-session projects during context window compaction. Use when running `/compact`, when auto-compact is triggered, or when determining what state to preserve across session boundaries to maintain continuity.
    0 installs
13. ▌
    Notion Batch Pattern · avizmarlon

    Use Notion REST API (not MCP) for batch operations (≥3 rows). Applies to database queries, batch updates, scans, pagination, file uploads, database creation, and page replication. MCP is acceptable only for single-page CRUD operations.
    0 installs
14. ▌
    Progress Md Business · avizmarlon

    PROGRESS.md as executive dashboard in business/product projects — track phase, metrics, milestones. Use when starting a business or product project, during MVP/phase tracking, when asking about project status dashboards, or when implementing impact metrics.
    0 installs
15. ▌
    Agent Continuity Loop · avizmarlon bundle

    Use for continuing, resuming, or closing substantial multi-session work; chained AI sessions; blind-AI handoff; living docs; roadmap/spec/progress/session-handoff/CHANGELOG updates; next slash goal or next-session prompt; Git/PR/worktree closeout. NOT for trivial one-off edits or urgent one-command ops.
    0 installs
16. ▌
    Engineering Standards · avizmarlon

    Engineering standards and project governance — Charter, RFC, Specification, Architecture Decision Records, Threat Models, SBOM, Runbooks, Playbooks, CHANGELOG, PROGRESS. CI/CD gates, branch protection, security review, dependency audit, secret scanning, TDD, feature flags. Use when scaffolding a non-trivial project, establishing governance, reviewing project structure, or asking about standards enforcement.
    0 installs
17. ▌
    Hooks For Enforcement · avizmarlon

    Hooks as enforcement mechanism for AI behavior — use when a written rule fails repeatedly in generation flow and deterministic structural enforcement is needed. Triggers include detecting cyclic rule failure, asking about Claude Code hooks/lifecycle events (SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, Stop), or when a behavior guard needs to execute outside the AI's inference loop.
    0 installs
18. ▌
    Hooks Multi Tool Parity · avizmarlon

    Enforce hook lifecycle synchronization across all AI agent tools. When creating, modifying, or removing hooks in any AI tool (Claude Code, Codex CLI, Cursor, Gemini, Kimi, etc.), propagate changes to all equivalent tools in the same session. Use when implementing cross-tool runtime enforcement.
    0 installs
19. ▌
    Local Service Autostart · avizmarlon

    Auto-start offline local services — detect connection errors, daemon failures, and start services programmatically instead of reporting them as blockers. Use when local service is unreachable, daemon not running, connection refused, port not listening, service offline.
    0 installs
20. ▌
    Notion API · avizmarlon

    Use Notion's REST API directly for batch database operations (querying, updating many rows, pagination, file uploads, creating databases). Auto-load when tasks mention Notion AND batch operations like "database", "update many", "iterate pages", "audit", "scan", or touch ≥3 rows. Prefer MCP (Notion search/create) for single-page CRUD only.
    0 installs
21. ▌
    New Project · avizmarlon

    Project bootstrap standard — guarantees all 25 core engineering and product disciplines are consulted in lifecycle order. Use when starting a new project, repository, feature, or phase. Prevents auto-trigger gaps by making the standard enforceable through a checklist.
    0 installs
22. ▌
    Docs As Code · avizmarlon

    Documentation accompanies code — no code is done without docs. Enforces a minimum documentation checklist per session, maintains a canonical documentation ledger across projects, and synchronizes documentation rules across all tools and agents. Use when writing code, creating features, modifying APIs, establishing new integrations, asking about documentation requirements, or managing documentation gates.
    0 installs
23. ▌
    Git Pr Rules · avizmarlon

    Always use Pull Requests — never merge locally into main. Workflow for coordinator sessions to batch-merge open PRs. Pre-work scan of open pull requests before starting feature/bug work. Use when working with git, mentioning merge, PR, pull request, gh pr, git push origin main, branch protection, squash merge, or code that targets main/master.
    0 installs
24. ▌
    Adr Spec Gate · avizmarlon

    ADR + Spec mandatory gate before any project or feature development. Architecture Decision Records and Software Design Docs enforce design clarity. Use when starting a new project, initiating non-trivial features, or discussing architecture decisions and design docs.
    0 installs
25. ▌
    Agent Flywheel · avizmarlon bundle

    Use when planning a new project or feature, turning an idea or specification into an executable plan, designing architecture, establishing a roadmap or phase, or coordinating multi-session or multi-agent builds. Activate on "plan this build", "turn this into tasks", "make it a plan", or when tasking/swarm coordination is mentioned. Skip routine bugfixes, urgent ops/incidents, or executing pre-approved plans unless re-planning is requested.
    0 installs
26. ▌
    Debug Protocol · avizmarlon

    Systematic debugging protocol for AI agents — pivot evidence-collection strategy after two failed reproduction rounds; treat available evidence (screenshots, console output, error messages) as ground truth from round one. Use when troubleshooting bugs, intermittent failures, error reproduction, or failed instrumentation.
    0 installs
27. ▌
    Tokens Taxonomy · avizmarlon

    API key and token strategy — one token per purpose, least-privilege separation, distinct scopes for CI/automation vs. manual operations vs. read-only access. Use when designing token/credential architecture, rotating credentials, setting up API access for multi-purpose systems, or implementing least-privilege token management.
    0 installs
28. ▌
    Iac First Commit · avizmarlon

    Infrastructure-as-Code from the first commit — every new project must be rebuildable from git clone + one command, with declarative state in code and idempotent execution. Use when scaffolding new projects, bootstrapping infrastructure, choosing IaC tools (Ansible/Terraform/SST/Fastlane), or setting up infra/, scripts/, or deployment automation.
    0 installs
29. ▌
    Version Bump Rules · avizmarlon

    Keep versions up-to-date — every production change bumps the version in the same commit. Semantic versioning rules. Special handling for WXT browser extensions (version in wxt.config.ts, not package.json). Use when working with version, release, semver, changelog, MAJOR.MINOR.PATCH, breaking change, or deploying code.
    0 installs
30. ▌
    Business Guardrails · avizmarlon

    Validate before building — enforce product/market fit analysis, competitive positioning, and scope discipline before implementation. Use when starting a new product, MVP definition, feature scope discussion, competitive analysis, or any business-facing decision that precedes development.
    0 installs
31. ▌
    Dns And Whois Tools · avizmarlon

    DNS lookup, WHOIS, passive-DNS history, IP reputation, and subdomain enumeration procedures. Auto-load when nslookup / dig / whois / host is mentioned, when investigating DNS records (A, NS, MX, CNAME, TXT), when researching historical nameservers, when checking IP reputation (AbuseIPDB, ipinfo.io), when enumerating subdomains (HackerTarget, crt.sh, SecurityTrails), or when reasoning about registrar vs hosting provider.
    0 installs