원클릭으로 Manus에서 모든 스킬 실행

update-full-stack-dev

스타0

포크0

업데이트2026년 3월 9일 17:54

Syncs eux-full-stack-dev.agent.md with current frontend and backend versions, patterns, and dependencies. Run when any part of the EUX stack changes.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

navikt

navikt/eux-architecture

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Update Full-Stack Dev Agent

Syncs .github/agents/eux-full-stack-dev.agent.md with the actual state of EUX projects.

When to run

Frontend dependencies updated (React, Aksel, Vite, Redux, etc.)
Backend frameworks updated (Spring Boot, Java, Kotlin)
eux-parent-pom updated
UI component patterns change (new Aksel version)

Steps

Read the current agent file at .github/agents/eux-full-stack-dev.agent.md.
Browse eux-web-app (navikt/eux-web-app):
- Check package.json for current versions: React, TypeScript, Vite, Redux Toolkit, Aksel (@navikt/ds-react), React Router, i18next, Express.
- Check vite.config.ts for build configuration changes.
- Check tsconfig.json for TypeScript config changes.
- Check server.mjs for BFF changes (auth flow, proxy routes).
- Look at a few components in src/components/ and src/pages/ for current UI patterns.
- Check if Aksel component usage has changed (e.g. new primitives, deprecated components).
- Check .github/agents/aksel.agent.md for Aksel design system updates.
Browse eux-parent-pom (navikt/eux-parent-pom, file pom.xml):
- Extract: Spring Boot version, Java target, Kotlin version.
Browse eux-neessi (navikt/eux-neessi, file pom.xml):
- Check Java version override, Lombok status, key dependencies.
Browse one Kotlin project (e.g. navikt/eux-nav-rinasak, file pom.xml):
- Check Java target version, module structure.
Update the agent file with findings. Keep it compact. Specifically update:
- Frontend tech stack versions (React, Vite, Aksel, TypeScript, etc.).
- Backend tech stack versions (Java, Kotlin, Spring Boot).
- Aksel sections if component API changed.
- Frontend patterns if component structure changed.
- Backend patterns if changed.
- Pitfalls section if new issues discovered.
- Remove any information that is no longer accurate.
Do not change: Domain terminology, architecture reference link, or core coding principles unless specifically wrong.
Commit with message describing what changed and why.

이 저장소의 다른 Skills

같은 저장소

sed-flyt-neessi-rina

navikt/eux-architecture

Generates a file showing how the content of a SED is mapped between Neessi-dto, ACL-SED and RINA-SED. Use this when asked to generate a SED flow mapping, sedFlyt, or field mapping for any SED type (e.g. H120, F001, H065).

2026-06-080

jira-ten-qa

navikt/eux-architecture

QA review of a TEN JIRA issue. Scores issue quality 1–10 and posts constructive feedback as a comment if the score is 7 or lower.

2026-04-070

odin-jira

navikt/eux-architecture

Analyzes a TEN JIRA issue, implements a fix across EUX repositories, creates PRs, and reports back to JIRA with results and reviewer tags.

2026-04-010

odin-plan

navikt/eux-architecture

Analyzes a TEN JIRA issue and posts an implementation plan as a comment. Does not implement anything — planning only.

2026-04-010

jira-ten

navikt/eux-architecture

Interact with JIRA using acli. Create, search, view, edit, comment, and transition issues in the TEN project.

2026-04-010

deploy-branch

navikt/eux-architecture

Pushes current branch to GitHub and triggers build/deploy workflows for EUX services. Safety: refuses to deploy from main. Frontend defaults to parallel.

2026-04-010

Update Full-Stack Dev Agent

Syncs .github/agents/eux-full-stack-dev.agent.md with the actual state of EUX projects.

When to run

Frontend dependencies updated (React, Aksel, Vite, Redux, etc.)

Backend frameworks updated (Spring Boot, Java, Kotlin)

eux-parent-pom updated

UI component patterns change (new Aksel version)

Steps

Read the current agent file at .github/agents/eux-full-stack-dev.agent.md.

Browse eux-web-app (navikt/eux-web-app):

Check package.json for current versions: React, TypeScript, Vite, Redux Toolkit, Aksel (@navikt/ds-react), React Router, i18next, Express.
Check vite.config.ts for build configuration changes.
Check tsconfig.json for TypeScript config changes.
Check server.mjs for BFF changes (auth flow, proxy routes).
Look at a few components in src/components/ and src/pages/ for current UI patterns.
Check if Aksel component usage has changed (e.g. new primitives, deprecated components).
Check .github/agents/aksel.agent.md for Aksel design system updates.

Browse eux-parent-pom (navikt/eux-parent-pom, file pom.xml):

Extract: Spring Boot version, Java target, Kotlin version.

Browse eux-neessi (navikt/eux-neessi, file pom.xml):

Check Java version override, Lombok status, key dependencies.

Browse one Kotlin project (e.g. navikt/eux-nav-rinasak, file pom.xml):

Check Java target version, module structure.

Update the agent file with findings. Keep it compact. Specifically update:

Frontend tech stack versions (React, Vite, Aksel, TypeScript, etc.).
Backend tech stack versions (Java, Kotlin, Spring Boot).
Aksel sections if component API changed.
Frontend patterns if component structure changed.
Backend patterns if changed.
Pitfalls section if new issues discovered.
Remove any information that is no longer accurate.

Do not change: Domain terminology, architecture reference link, or core coding principles unless specifically wrong.

Commit with message describing what changed and why.

name	update-full-stack-dev
description	Syncs eux-full-stack-dev.agent.md with current frontend and backend versions, patterns, and dependencies. Run when any part of the EUX stack changes.