Codync
무료 오픈소스 1:1 대안, Grok Bot과 Muse 대신
Prumo는 프레임워크·데이터베이스 규칙·테스트 범위를 미리 선택해 TypeScript 프로젝트를 시작하고 자동으로 적용
Prumo starts a TypeScript project with the framework, the database rules and the test boundaries already chosen, and writes every one of them into the project.
개발 도구TypeScript · CSSGitHub @stjosephworks온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기메이커가 쓴 소개는 위의 한 줄이 전부입니다. 더 자세한 내용은 저장소 README에서 읽을 수 있습니다. 저장소 README ↗
README 전체를 불러오는 중입니다.
README 전문 보기 ↗The public website for Prumo and Prumo Desktop, published at prumo.stjosephworks.org.
It was generated by Prumo itself, as a site project, and follows the conventions in .prumo/ like any
other generated project. That is deliberate: a tool whose answer for a public page is Next on the App
Router has no business publishing its own page on anything else.
Every document has exactly one home.
| Content | Lives in |
|---|---|
| The getting-started path, the conventions explainer, the command reference, the Desktop page | This repository, in src/app/[lang]/ |
README.md, docs/stack.md, docs/structure.md and the rest | prumo and prumo-desktop, fetched at build |
Nothing in the second row is retyped here. content/documents.json lists each one with the repository, the
path, the commit it is pinned to and the route it becomes; scripts/fetch-docs.mjs downloads exactly those
files into content/fetched/, which is not committed. A file that does not answer fails the build.
The same manifest also reads cli/package.json at that commit, so the version in the footer is the one the
pinned commit publishes rather than a number kept by hand.
There are no tags to pin to: releasing the CLI is a version bump landing on main. So the pins are commit
SHAs, raised by editing content/documents.json. That commit is also what redeploys the site, so no webhook
is needed from the other repositories.
English, Portuguese and Spanish, under /en, /pt and /es. Each language is one entry in
src/features/i18n/locales.ts, with its dictionary in
src/features/i18n/dictionaries/ and its blurb for each document in content/documents.json; the tests walk every
entry, so a new language fails them until all of it is written. Only the pages this repository writes are
translated; the fetched documents are rendered in English in every language with a note saying so, because
translating them would rebuild in other languages the duplication the manifest exists to avoid.
A path without a locale, / included, is answered by src/proxy.ts with a redirect to the visitor's language: the
one picked in the language menu, kept for a year in the locale cookie, else the first one their browser accepts
(pt-PT reaching pt), else English. A path that names a locale is never redirected.
This repository departs from prumo's rule that every file is written in English, and only there:
Portuguese and Spanish are allowed in the translated content. Every identifier, comment and commit message stays
English.
pnpm install
pnpm dev
The site runs on http://localhost:3200. / redirects to the visitor's language; see Languages.
| Command | What it does |
|---|---|
pnpm fetch:docs | Downloads the pinned documents. Runs automatically before dev, build, test and typecheck |
pnpm test | Checks the manifest, the dictionaries, and that every search anchor exists in the rendered page |
pnpm lint | Biome |
pnpm typecheck | Next's route types, then tsc --noEmit |
pnpm build · pnpm start | Production build, then serves it |
dev-logs/ holds how this site was decided, kept for context and referenced by nothing: not by this README,
not by the manifest, not by a page. Read it to understand why something is the way it is, never to learn
what is in force.