Medical Research Skills for Claude Code, Codex, Cursor & Copilot
58 open-source skills for the full medical research lifecycle. Built by physicians, tested on real publications.
An open encyclopedic database for the study of psychopharmacology
HealthTypeScript · JavaScriptGitHub @josikinzzOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
An open dataset and encyclopedia of psychoactive substances: dose, duration, effects, interactions, chemistry, and legality. Source for dose.wiki.
Taken from the repository README
Loading the full README.
Read the full README ↗This repository is the Next.js application behind dose.wiki and its Effect Index publication. PlanetScale Postgres is the runtime database. The protected /dev surface holds the editorial tools.
dose.wiki synthesizes factual knowledge about psychoactive substances from harm-reduction and reference sources into a single open dataset. It aims to establish an open standard for psychopharmacology datasets, supporting research and education.
The factual knowledge within substance articles draw on decades of documentation by scientists, psychonauts, and the harm-reduction community, gathered from ten harm-reduction and reference resources. Each article links to the source pages that informed it.
Substance articles were drafted by LLMs, with dosage information transcribed by software from online tables. Real life human beings then reviewed and carefully edited each output over the course of months. The how articles are made explains the process in depth.
So, why did we use LLMs as part of this process? This was done for several reasons, but primarily speed, practicality, and reproducibility. Josie Kins, a co-founder of this project, the founder of PsychonautWiki, and numerous other similar projects, has real-world experience hand-crafting substance encyclopedias with teams of human beings. We know what it takes. It is an incredibly arduous and long term process. For example, the first draft of psychonautwiki took an entire community of people from 2011-2016. With incredibly few people reliably sticking around, and their workflows always leaving with them. Our community doesn't need a modern and open platform in 5 years from now. We need one yesterday.
This is why factual knowledge from across the internet was carefully scraped from online resources, assembled into either mechanistic parsers or an LLM synthesis pipeline, and aggregated into a single beautifully machine readable dataset, for anybody to download. A process that was followed by months of human review before we felt comfortable publishing it, and in total took about a year to complete. We deeply care about what we are doing here, and are now building as humans on top of this new open standard.
dose.wiki is in beta. Each article's Article Status section tracks its progress and identifies whether it has been human-reviewed. Review is essential to trustworthiness: reviewers verify pharmacology, check dosage and interactions for potentially harmful errors, and add corrections, references, and their own explanations. Errors can have serious real-world consequences, so we welcome anyone able to submit feedback via the forms at the bottom of each substance article!
The other collections are entirely human-created:
The site and dataset continue to evolve toward 1.0. Check back for updates, or send questions, comments, and corrections.
Public pages live under src/app/. Representative route groups are:
/substances, /[slug], /articles, and /articles/[slug];/effects, /effects/[effectSlug], /reports, and /reports/[slug];/replications and /replications/[slug];/category/[categoryKey], /chemical-classes/[classKey], /mechanism/[mechanismSlug], /psychoactive/[...summaryPath], and /search;/about, /contributors/[profileKey], /docs/how, /docs/code, and /docs/license.Some pages are publication-specific. src/config/siteFlavor.ts defines the flavor contract, and lib/next/flavorGatedRoutes.ts enforces it. The src/app/**/page.tsx files are the current route map. Compatibility redirects and aliases live in src/middleware.ts and lib/next/publicRouteAliases.ts.
The routes above are live at https://dose.wiki/ and https://www.dose.wiki/. Pre-launch /preview addresses permanently redirect to the matching unprefixed route.
The read-only API at https://dose.wiki/api/v1 (OpenAPI 3.1 at
https://dose.wiki/api/v1/openapi.json) exposes substance records, normalized
reagent tests, molecule SVGs, and replication collections. The complete
consumer contract, including the canonical replication embed at
/embed/replications and its versioned message protocol, is
docs/api.md. Use OpenAPI rather than this README for paths and
response shapes.
DoseWiki content is for harm-reduction education and is not medical advice. Review the license and reuse terms and preserve source attribution.
Sign in at /sign-in. The protected editor is mounted at /dev with tab and item deep links.
The editor groups related work rather than exposing separate applications:
DEV_TAB_REGISTRY in src/features/dev/pages/devTabRegistry.ts is the tab inventory. src/features/dev/pages/DevModePageView.tsx renders the tabs, and src/features/dev/pages/devModePageUtils.ts normalizes deep links.
Auth.js supplies identity, and the Postgres memberships table supplies roles. Auth covers accounts, roles, and route protection. Editor tool handlers live under src/app/api/dev/. Article saves go through src/app/api/save-article/. Named rate-limit policies live in lib/http/rateLimitPolicy.ts.
bun install --frozen-lockfile
bun run dev
CONTRIBUTING.md covers setup, local tools, and verification. ARCHITECTURE.md maps the repository, and docs/README.md indexes the rest of the documentation. The visual codebase overview is at /docs/code, and the article process is at /docs/how.