← all publishers

navikt

@navikt source repo

Report this profile Claim this profile

• 125 skills
• 0 followers
• 5 hours ago last updated

1. ▌
   Doctor 2 · navikt

   Audit whether the current repository and session are ready for effective Grillmester use in OpenCode v1. Use only when the user explicitly asks to check, diagnose, or understand the OpenCode setup; the audit is read-only.
   0
   installs
2. ▌
   Review 2 · navikt

   Self-review the complete scoped diff for correctness, regressions, requirements and repository rules before delivery. Use after implementation or when asked to find problems in changes; use `security-review` for security-specific analysis.
   0
   installs
3. ▌
   Triage 2 · navikt bundle

   Assess incoming issues or pull requests, verify claims and prepare work-ready briefs. Use for inbox review, bug-report assessment or readiness decisions; use `issue-management` for tracker mutations and `review` for a completed implementation diff.
   0
   installs
4. ▌
   Dulting 2 · navikt bundle

   Design and evaluate responsible behavioral interventions in public services. Use for reminders, defaults, friction or experiments intended to change a specific user behavior; use `klarsprak` when the task is only to clarify wording.
   0
   installs
5. ▌
   Handoff 2 · navikt

   Prepare a portable handoff when the user requests transferring work to another session, client, or colleague. Ordinary context compression and same-session delegation belong to the client.
   0
   installs
6. ▌
   To Spec 2 · navikt

   Document resolved requirements and design choices as a concise implementation plan or specification, including a requested local document. Use `grill-with-docs` for unresolved design choices and `to-issues` for several independently deliverable slices.
   0
   installs
7. ▌
   Grill Me 2 · navikt

   Run an explicitly requested standalone stress-test of a plan, proposal, or idea. Use when the user asks to be grilled; expose weak assumptions and resolve choices in conversation without automatically creating documentation or a decision map.
   0
   installs
8. ▌
   Grilling 2 · navikt

   Clarify a request and challenge a plan's assumptions, requirements, and trade-offs through one question at a time. Use for unresolved intent or design choices, and as Grillmester's opening method; grill-with-docs adds durable domain documentation and Wayfinder organizes dependent decisions.
   0
   installs
9. ▌
   E2e Tests 2 · navikt

   Create full-system tests that boot the application and prove an observable user or system flow. Use when the assembled app, its entry point and final outcome must work together; use `integration-tests` for a narrow real adapter without full application boot.
   0
   installs
10. ▌
    Klarsprak 2 · navikt bundle

    Write or edit clear Norwegian prose while preserving technical meaning and established domain terms. Use for unclear user-facing copy, documentation or PR text; use `dulting` when the task is to influence behavior through an intervention.
    0
    installs
11. ▌
    Prototype 2 · navikt

    Build a bounded, runnable throwaway experiment to resolve uncertain behavior or an interface contract. Use for data models, state machines, event flows, retries or failure semantics; use `design-prototype` for visual layouts and user-flow sketches.
    0
    installs
12. ▌
    To Issues 2 · navikt

    Turn a resolved plan or specification into independently useful implementation issues with native dependencies. Use when the user asks to break work into tickets; use `wayfinder` for unresolved decisions and `issue-management` for tracker mechanics.
    0
    installs
13. ▌
    Wayfinder 2 · navikt bundle

    Organize several unresolved, dependent decisions as a persistent shared issue map when a conversation checkpoint cannot keep the route navigable across sessions. Select automatically from that need or continue an existing map; use grill-with-docs for each design decision, and ordinary planning when the direction is already settled.
    0
    installs
14. ▌
    API Design 2 · navikt

    Design or change a published API or event contract using consumer and compatibility evidence. Use for new endpoints, versioning, breaking changes or deprecation; use `kotlin-ktor` for framework implementation and `architecture-review` for wider system boundaries.
    0
    installs
15. ▌
    Tdd 3 · navikt bundle

    Develop behavior in small red-green-refactor cycles through public interfaces. Use for requested test-first development or a confirmed bug requiring a failing regression test; use `diagnosing-bugs` to find an unclear cause and `integration-tests` or the repository's full-system test workflow to choose the test boundary.
    0
    installs
16. ▌
    Kafka Topic 2 · navikt bundle

    Design, implement or review Kafka topics and event flows from producer to consumer. Use for event contracts, keys, consumer groups, delivery guarantees or failure handling; use `nav-troubleshoot` for runtime incident evidence and `api-design` for wider contract compatibility.
    0
    installs
17. ▌
    Kotlin Ktor 2 · navikt bundle

    Implement or review Kotlin and Ktor application behavior, configuration, clients and lifecycle. Use when changing a Ktor backend; use `api-design` for public contract choices and `auth-overview` for identity and authorization mechanisms.
    0
    installs
18. ▌
    Lumi Survey 2 · navikt bundle

    Integrate or review @navikt/lumi-survey from frontend configuration through verified feedback submission. Use for Lumi widgets, survey choices, transport or privacy-safe context; use `auth-overview` for shared authentication design beyond the Lumi integration.
    0
    installs
19. ▌
    Team Status 2 · navikt bundle

    Summarize team status, goal progress and priorities from confirmed work and outcome evidence. Use for weekly updates, period reviews or cross-repository overviews; use `okr` to formulate goals and `triage` to assess individual incoming issues.
    0
    installs
20. ▌
    Aksel Design 2 · navikt bundle

    Choose Aksel components, semantic tokens and responsive patterns for Nav interfaces. Use when designing or changing layout, forms or styling with @navikt/ds-react; use `accessibility-review` to verify the resulting user flow.
    0
    installs
21. ▌
    Pull Request 2 · navikt

    Prepare and publish a pull request for a verified, scoped change when the user asks to open or update a PR. Use `review` to assess the diff first; implementing or reviewing work alone does not authorize publication.
    0
    installs
22. ▌
    Auth Overview 2 · navikt bundle

    Design, implement or diagnose authentication and authorization in a Nav backend. Use for token validation, token exchange, protected endpoints or issuer, audience and 401/403 problems; use `security-review` for a broader security assessment.
    2
    installs
23. ▌
    Guided Review 2 · navikt

    Guide a human through a pull request or resolved diff one reading step at a time, then prepare review findings. Manually invoke this workflow for an interactive assessment; use `review` for the normal self-review pass.
    0
    installs
24. ▌
    Nais Manifest 2 · navikt bundle

    Create, change or review Nais Application and Naisjob deployment resources. Use for ingress, probes, resource limits, access policies, scaling or scheduled jobs; use `nav-troubleshoot` to diagnose a live workload and specialist skills for application code.
    0
    installs
25. ▌
    Readme Update 2 · navikt

    Create or update a README from verified implementation and operational evidence. Use when repository purpose, setup, usage or ownership documentation is missing or stale; use `klarsprak` for a wording-only edit and `to-spec` for intended future behavior.
    0
    installs
26. ▌
    Doctor 3 · navikt

    Audit whether the current repository and session are ready for effective Grillmester use in OpenCode v1. Use only when the user explicitly asks to check, diagnose, or understand the OpenCode setup; the audit is read-only.
    0
    installs
27. ▌
    Tdd 4 · navikt bundle

    Develop behavior in small red-green-refactor cycles through public interfaces. Use for requested test-first development or a confirmed bug requiring a failing regression test; use `diagnosing-bugs` to find an unclear cause and `integration-tests` or the repository's full-system test workflow to choose the test boundary.
    0
    installs
28. ▌
    Review 3 · navikt

    Self-review the complete scoped diff for correctness, regressions, requirements and repository rules before delivery. Use after implementation or when asked to find problems in changes; use `security-review` for security-specific analysis.
    0
    installs
29. ▌
    Create A Skill 2 · navikt bundle

    Create, revise, review, or diagnose a portable Agent Skill for OpenCode v1, including native discovery, permissions, and an optional slash-command adapter. Use when a user asks to create or improve a skill, investigate why one does not load, or validate skill behavior.
    0
    installs
30. ▌
    Figma Workflow 2 · navikt

    Translate a chosen Figma design into Aksel code or an implementation brief with component, token and responsive guidance. Use for design-to-code work; use `design-prototype` for visual exploration or changes to the Figma design itself. Design-only agents return a brief.
    0
    installs
31. ▌
    Produktledelse 2 · navikt bundle

    Explore product opportunities, user needs, assumptions and initiative risks. Use for discovery planning, user interviews or product-lead reflection; use `okr` for measurable goals and `workshop-design` for a facilitated group session.
    0
    installs
32. ▌
    Diagnosing Bugs 2 · navikt bundle

    Diagnose failures, hangs, flakes or performance regressions from reproduction, code and runtime evidence. Use when the cause is unclear; use `tdd` for an established fix and `nav-troubleshoot` when the missing evidence is in a deployed Nais environment.
    0
    installs
33. ▌
    Domain Modeling 2 · navikt bundle

    Challenge and maintain canonical domain terminology and qualifying architectural decisions during authorized design work. Use when concepts, boundaries, or durable trade-offs change; reading existing vocabulary alone does not need this skill.
    0
    installs
34. ▌
    Grill With Docs 2 · navikt

    Resolve open requirements, assumptions or design choices against the repository's domain model, recording agreed terms and qualifying decisions. Use for coherent design clarification; use `to-spec` to capture a settled plan and `wayfinder` for dependent decisions needing a persistent map.
    0
    installs
35. ▌
    Security Review 2 · navikt bundle

    Assess a design or change for security and privacy risks. Use for sensitive data, identity, authorization, trust boundaries, privileged operations or a requested security review; use `auth-overview` to implement an authentication mechanism and `architecture-review` for broader design trade-offs.
    0
    installs
36. ▌
    Workshop Design 2 · navikt bundle

    Design a facilitated workshop with an outcome, agenda, participation structure and follow-up. Use for group exploration, alignment, decisions, retrospectives or team health; use `produktledelse` for individual discovery guidance and `okr` for goal formulation.
    0
    installs
37. ▌
    Design Prototype 2 · navikt bundle

    Explore or refine visual concepts, user flows and existing Figma designs through Aksel browser sketches or editable Figma components. Use for layout, hierarchy and visual alternatives; use `prototype` for executable behavior and `figma-workflow` to translate a chosen design into code or an implementation brief.
    0
    installs
38. ▌
    Issue Management 2 · navikt

    Inspect, create, update, link or close GitHub issues for work that is already shaped. Use for tracker mechanics and explicit issue requests; use `triage` to assess readiness and `to-issues` to decompose a resolved plan.
    0
    installs
39. ▌
    Nav Troubleshoot 2 · navikt bundle

    Diagnose deployed Nais workload failures using deployment, pod, log, metric and trace evidence. Use for production-only errors, failed deploys, restarts or connectivity problems; use `diagnosing-bugs` once a code defect needs reproduction and a fix.
    0
    installs
40. ▌
    Review 4 · navikt

    Self-review the complete scoped diff for correctness, regressions, requirements and repository rules before delivery. Use after implementation or when asked to find problems in changes; use `security-review` for security-specific analysis.
    0
    installs
41. ▌
    Integration Tests 2 · navikt

    Create narrow tests through a real adapter or boundary using its public interface. Use for database, HTTP-client, message-adapter or filesystem contracts; use `e2e-tests` when proving the flow requires booting the assembled application.
    0
    installs
42. ▌
    Postgresql Review 2 · navikt bundle

    Design or review PostgreSQL schemas, queries, transactions, migrations and connection capacity. Use for slow queries, pool sizing, data integrity or database changes; use `nav-troubleshoot` for deployed incident evidence and `architecture-review` for broader storage decisions.
    0
    installs
43. ▌
    Architecture Review 2 · navikt bundle

    Evaluate a consequential architecture proposal, its alternatives, migration and reversibility. Use for new services, cross-team boundaries, platform choices or costly migrations; use `improve-codebase-architecture` to discover refactoring candidates in existing code and `security-review` for security analysis.
    0
    installs
44. ▌
    Observability Setup 2 · navikt bundle

    Add or improve service metrics, structured logs, traces, health signals, dashboards and alerts. Use when instrumentation or operational visibility is missing or misleading; use `nav-troubleshoot` to investigate an active incident with existing telemetry.
    0
    installs
45. ▌
    Accessibility Review 2 · navikt

    Review a Nav frontend flow for accessibility using keyboard, screen-reader, contrast, focus, form and axe evidence. Use when checking an interface before delivery or investigating an accessibility defect; use `aksel-design` for component selection and layout.
    0
    installs
46. ▌
    Create A Skill 3 · navikt bundle

    Create, revise, review, or diagnose a portable Agent Skill for OpenCode v1, including native discovery, permissions, and an optional slash-command adapter. Use when a user asks to create or improve a skill, investigate why one does not load, or validate skill behavior.
    0
    installs
47. ▌
    Diagnosing Bugs 3 · navikt bundle

    Diagnose failures, hangs, flakes or performance regressions from reproduction, code and runtime evidence. Use when the cause is unclear; use `tdd` for an established fix and the repository's platform diagnostic workflow when the missing evidence is in a deployed Nais environment.
    0
    installs
48. ▌
    Issue Management 3 · navikt

    Inspect, create, update, link or close GitHub issues for work that is already shaped. Use for tracker mechanics and explicit issue requests; use the full-context issue assessment workflow to assess readiness and the full-context plan decomposition workflow to decompose a resolved plan.
    0
    installs
49. ▌
    Integration Tests 3 · navikt

    Create narrow tests through a real adapter or boundary using its public interface. Use for database, HTTP-client, message-adapter or filesystem contracts; use the repository's full-system test workflow when proving the flow requires booting the assembled application.
    0
    installs
50. ▌
    Diagnosing Bugs 4 · navikt bundle

    Diagnose failures, hangs, flakes or performance regressions from reproduction, code and runtime evidence. Use when the cause is unclear; use `tdd` for an established fix and the repository's platform diagnostic workflow when the missing evidence is in a deployed Nais environment.
    0
    installs
51. ▌
    Issue Management 4 · navikt

    Inspect, create, update, link or close GitHub issues for work that is already shaped. Use for tracker mechanics and explicit issue requests; use the full-context issue assessment workflow to assess readiness and the full-context plan decomposition workflow to decompose a resolved plan.
    0
    installs
52. ▌
    Integration Tests 4 · navikt

    Create narrow tests through a real adapter or boundary using its public interface. Use for database, HTTP-client, message-adapter or filesystem contracts; use the repository's full-system test workflow when proving the flow requires booting the assembled application.
    0
    installs
53. ▌
    Improve Codebase Architecture 2 · navikt bundle

    Find refactoring opportunities that simplify module boundaries and improve testability and navigation. Use when existing code is tightly coupled, shallow or hard to change; use `architecture-review` to evaluate a concrete architecture proposal.
    0
    installs
54. ▌
    Okr 2 · navikt bundle

    Formulate and review measurable product outcomes with objectives, key results, baselines and evidence. Use for goal setting or turning delivery lists into outcome measures; use `team-status` to report progress against existing goals.
    0
    installs
55. ▌
    Tdd 2 · navikt bundle

    Develop behavior in small red-green-refactor cycles through public interfaces. Use for requested test-first development or a confirmed bug requiring a failing regression test; use `diagnosing-bugs` to find an unclear cause and `integration-tests` or `e2e-tests` to choose the test boundary.
    0
    installs
56. ▌
    Okr · navikt bundle

    Formulate and review measurable product outcomes with objectives, key results, baselines and evidence. Use for goal setting or turning delivery lists into outcome measures; use `team-status` to report progress against existing goals.
    0
    installs
57. ▌
    Tdd · navikt bundle

    Develop behavior in small red-green-refactor cycles through public interfaces. Use for requested test-first development or a confirmed bug requiring a failing regression test; use `diagnosing-bugs` to find an unclear cause and `integration-tests` or `e2e-tests` to choose the test boundary.
    0
    installs
58. ▌
    Doctor · navikt

    Audits whether the current repository is ready for effective Grillmester use across Copilot CLI, the Copilot app, cloud agent, and Copilot code review. Use only when the user explicitly asks to check, diagnose, or understand the repository's Grillmester setup; the audit is read-only.
    0
    installs
59. ▌
    Review · navikt

    Self-review the complete scoped diff for correctness, regressions, requirements and repository rules before delivery. Use after implementation or when asked to find problems in changes; use `security-review` for security-specific analysis.
    0
    installs
60. ▌
    Triage · navikt bundle

    Assess incoming issues or pull requests, verify claims and prepare work-ready briefs. Use for inbox review, bug-report assessment or readiness decisions; use `issue-management` for tracker mutations and `review` for a completed implementation diff.
    0
    installs
61. ▌
    Dulting · navikt bundle

    Design and evaluate responsible behavioral interventions in public services. Use for reminders, defaults, friction or experiments intended to change a specific user behavior; use `klarsprak` when the task is only to clarify wording.
    0
    installs
62. ▌
    Handoff · navikt

    Prepare a portable handoff when the user requests transferring work to another session, client, or colleague. Ordinary context compression and same-session delegation belong to the client.
    0
    installs
63. ▌
    To Spec · navikt

    Document resolved requirements and design choices as a concise implementation plan or specification, including a requested local document. Use `grill-with-docs` for unresolved design choices and `to-issues` for several independently deliverable slices.
    0
    installs
64. ▌
    Grill Me · navikt

    Run an explicitly requested standalone stress-test of a plan, proposal, or idea. Use when the user asks to be grilled; expose weak assumptions and resolve choices in conversation without automatically creating documentation or a decision map.
    0
    installs
65. ▌
    Grilling · navikt

    Clarify a request and challenge a plan's assumptions, requirements, and trade-offs through one question at a time. Use for unresolved intent or design choices, and as Grillmester's opening method; grill-with-docs adds durable domain documentation and Wayfinder organizes dependent decisions.
    0
    installs
66. ▌
    E2e Tests · navikt

    Create full-system tests that boot the application and prove an observable user or system flow. Use when the assembled app, its entry point and final outcome must work together; use `integration-tests` for a narrow real adapter without full application boot.
    0
    installs
67. ▌
    Prototype · navikt

    Build a bounded, runnable throwaway experiment to resolve uncertain behavior or an interface contract. Use for data models, state machines, event flows, retries or failure semantics; use `design-prototype` for visual layouts and user-flow sketches.
    0
    installs
68. ▌
    To Issues · navikt

    Turn a resolved plan or specification into independently useful implementation issues with native dependencies. Use when the user asks to break work into tickets; use `wayfinder` for unresolved decisions and `issue-management` for tracker mechanics.
    0
    installs
69. ▌
    Wayfinder · navikt bundle

    Organize several unresolved, dependent decisions as a persistent shared issue map when a conversation checkpoint cannot keep the route navigable across sessions. Select automatically from that need or continue an existing map; use grill-with-docs for each design decision, and ordinary planning when the direction is already settled.
    0
    installs
70. ▌
    Kafka Topic · navikt bundle

    Design, implement or review Kafka topics and event flows from producer to consumer. Use for event contracts, keys, consumer groups, delivery guarantees or failure handling; use `nav-troubleshoot` for runtime incident evidence and `api-design` for wider contract compatibility.
    0
    installs
71. ▌
    Kotlin Ktor · navikt bundle

    Implement or review Kotlin and Ktor application behavior, configuration, clients and lifecycle. Use when changing a Ktor backend; use `api-design` for public contract choices and `auth-overview` for identity and authorization mechanisms.
    0
    installs
72. ▌
    Lumi Survey · navikt bundle

    Integrate or review @navikt/lumi-survey from frontend configuration through verified feedback submission. Use for Lumi widgets, survey choices, transport or privacy-safe context; use `auth-overview` for shared authentication design beyond the Lumi integration.
    0
    installs
73. ▌
    Team Status · navikt bundle

    Summarize team status, goal progress and priorities from confirmed work and outcome evidence. Use for weekly updates, period reviews or cross-repository overviews; use `okr` to formulate goals and `triage` to assess individual incoming issues.
    0
    installs
74. ▌
    Aksel Design · navikt bundle

    Choose Aksel components, semantic tokens and responsive patterns for Nav interfaces. Use when designing or changing layout, forms or styling with @navikt/ds-react; use `accessibility-review` to verify the resulting user flow.
    0
    installs
75. ▌
    Pull Request · navikt

    Prepare and publish a pull request for a verified, scoped change when the user asks to open or update a PR. Use `review` to assess the diff first; implementing or reviewing work alone does not authorize publication.
    0
    installs
76. ▌
    Auth Overview · navikt bundle

    Design, implement or diagnose authentication and authorization in a Nav backend. Use for token validation, token exchange, protected endpoints or issuer, audience and 401/403 problems; use `security-review` for a broader security assessment.
    0
    installs
77. ▌
    Guided Review · navikt

    Guide a human through a pull request or resolved diff one reading step at a time, then prepare review findings. Manually invoke this workflow for an interactive assessment; use `review` for the normal self-review pass.
    0
    installs
78. ▌
    Nais Manifest · navikt bundle

    Create, change or review Nais Application and Naisjob deployment resources. Use for ingress, probes, resource limits, access policies, scaling or scheduled jobs; use `nav-troubleshoot` to diagnose a live workload and specialist skills for application code.
    0
    installs
79. ▌
    Readme Update · navikt

    Create or update a README from verified implementation and operational evidence. Use when repository purpose, setup, usage or ownership documentation is missing or stale; use `klarsprak` for a wording-only edit and `to-spec` for intended future behavior.
    0
    installs
80. ▌
    Create A Skill · navikt bundle

    Create, improve or diagnose a GitHub Copilot CLI skill and validate its discovery and behavior. Use when authoring instructions, correcting triggers or testing skill selection; explicit repository setup audits belong to `doctor`.
    0
    installs
81. ▌
    Figma Workflow · navikt

    Translate a chosen Figma design into Aksel code or an implementation brief with component, token and responsive guidance. Use for design-to-code work; use `design-prototype` for visual exploration or changes to the Figma design itself. Design-only agents return a brief.
    0
    installs
82. ▌
    Produktledelse · navikt bundle

    Explore product opportunities, user needs, assumptions and initiative risks. Use for discovery planning, user interviews or product-lead reflection; use `okr` for measurable goals and `workshop-design` for a facilitated group session.
    0
    installs
83. ▌
    Diagnosing Bugs · navikt bundle

    Diagnose failures, hangs, flakes or performance regressions from reproduction, code and runtime evidence. Use when the cause is unclear; use `tdd` for an established fix and `nav-troubleshoot` when the missing evidence is in a deployed Nais environment.
    0
    installs
84. ▌
    Domain Modeling · navikt bundle

    Challenge and maintain canonical domain terminology and qualifying architectural decisions during authorized design work. Use when concepts, boundaries, or durable trade-offs change; reading existing vocabulary alone does not need this skill.
    0
    installs
85. ▌
    Grill With Docs · navikt

    Resolve open requirements, assumptions or design choices against the repository's domain model, recording agreed terms and qualifying decisions. Use for coherent design clarification; use `to-spec` to capture a settled plan and `wayfinder` for dependent decisions needing a persistent map.
    0
    installs
86. ▌
    Workshop Design · navikt bundle

    Design a facilitated workshop with an outcome, agenda, participation structure and follow-up. Use for group exploration, alignment, decisions, retrospectives or team health; use `produktledelse` for individual discovery guidance and `okr` for goal formulation.
    0
    installs
87. ▌
    Design Prototype · navikt bundle

    Explore or refine visual concepts, user flows and existing Figma designs through Aksel browser sketches or editable Figma components. Use for layout, hierarchy and visual alternatives; use `prototype` for executable behavior and `figma-workflow` to translate a chosen design into code or an implementation brief.
    0
    installs
88. ▌
    Issue Management · navikt

    Inspect, create, update, link or close GitHub issues for work that is already shaped. Use for tracker mechanics and explicit issue requests; use `triage` to assess readiness and `to-issues` to decompose a resolved plan.
    0
    installs
89. ▌
    Integration Tests · navikt

    Create narrow tests through a real adapter or boundary using its public interface. Use for database, HTTP-client, message-adapter or filesystem contracts; use `e2e-tests` when proving the flow requires booting the assembled application.
    0
    installs
90. ▌
    Architecture Review · navikt bundle

    Evaluate a consequential architecture proposal, its alternatives, migration and reversibility. Use for new services, cross-team boundaries, platform choices or costly migrations; use `improve-codebase-architecture` to discover refactoring candidates in existing code and `security-review` for security analysis.
    0
    installs
91. ▌
    Accessibility Review · navikt

    Review a Nav frontend flow for accessibility using keyboard, screen-reader, contrast, focus, form and axe evidence. Use when checking an interface before delivery or investigating an accessibility defect; use `aksel-design` for component selection and layout.
    0
    installs
92. ▌
    Improve Codebase Architecture · navikt bundle

    Find refactoring opportunities that simplify module boundaries and improve testability and navigation. Use when existing code is tightly coupled, shallow or hard to change; use `architecture-review` to evaluate a concrete architecture proposal.
    0
    installs
93. ▌
    Workstation Security · navikt bundle

    Sikkerhetssjekk for macOS-utviklermaskiner — brannmur, SSH, Git, hemmeligheter, nettverk og Nav-plattformverktøy
    0
    installs
94. ▌
    Nav Architecture Review · navikt bundle

    Generer Architecture Decision Records (ADR) med flerperspektiv-review tilpasset Nav
    0
    installs
95. ▌
    Observability Debugging · navikt bundle

    Feilsøk produksjonsproblemer med Mimir-metrikker, Loki-logger og Tempo-traces — strukturerte debugging-workflows for Nav-utviklere
    0
    installs
96. ▌
    Nav Dekoratoren · navikt bundle

    Integrer og konfigurer Nav Dekoratøren – felles header og footer for nav.no-applikasjoner. Bruk når et team skal ta i bruk Dekoratøren, oppdatere konfigurasjon, legge til breadcrumbs/språkvelger/analytics, håndtere samtykke (ekomloven), CSP eller feilsøke integrasjon mot dekoratøren.
    0
    installs
97. ▌
    Security Review · navikt bundle

    Bruk før commit, push eller pull request for å sjekke at koden er trygg å merge
    0
    installs
98. ▌
    AI News Research · navikt bundle

    Skriv månedlige oppsummeringer av AI-nyheter for utviklere på norsk med fungerende kildelenker. Bruk for å skrive nyheter, oppsummere AI-trender, lage månedlig oppdatering, eller undersøke hva som er nytt i GitHub Copilot, coding agents, AGENTS.md, skills, memory, agentic workflows eller developer experience.
    0
    installs
99. ▌
    Flyway Migration · navikt bundle

    Databasemigrasjonsmønstre med Flyway og versjonerte SQL-skript
    0
    installs
100. ▌
     Nav Troubleshoot · navikt bundle

     Strukturerte diagnostiske trær for vanlige Nav-plattformproblemer — pod-krasj, auth-feil, Kafka-lag og databaseproblemer
     0
     installs