opp-radar
面向个人开发者 / 技术创业者的"机会雷达"提示词仓库:从公开技术信号里筛出小团队能做的中小产品机会,写成渠道无关的文章 .md + 封面 .png。
本仓库只负责"生成"——渲染排版和推送到公众号草稿箱由独立项目 wechat-auto-publish 负责。
专栏名:开发者机会观察(公众号:程序员白大力)。觉得有用欢迎关注。
目录结构
opp-radar/
prompts/
dev.md # 开发者机会观察(dev 领域)完整提示词:找信号→反向验证→写稿→封面
# 以后加 marketing.md、xxx.md 等其他领域提示词
examples/
开发者机会观察-第5期.md/.png # 一篇成稿样例(纯生成产物)
tests/ # 冒烟测试
.github/workflows/publish.yml # CI:构建 + TestPyPI/PyPI(OIDC 免密)
pyproject.toml # 打包配置
跑一期(生成)
按 prompts/dev.md 的流程:找信号 → 反向验证 → 写 5-8 个全新方向 → 出一张封面。
产出 <主名>.md 和 <主名>.png,落在本地文章目录(不进本仓库)。
渲染和推草稿请交给 wechat-auto-publish:
pip install wechat-auto-publish
wechat-auto-publish draft "<主名>.md" "<主名>.png" "<标题>" "<摘要>"
样例
examples/开发者机会观察-第5期.md + .png 是一期纯生成产物的样子(科技风经典蓝的最终排版由 wechat-auto-publish 渲染)。
设计原则
- 提示词只讲"做什么",调度/定时是外层平台壳,不写进提示词;
- 生成与分发分离:opp-radar 出文本,wechat-auto-publish 负责渲染和发布;
- 文章产出与代码仓库隔离,不随仓库分发。
配套项目
生成完文章后,想一键渲染成公众号排版并推到草稿箱?看 wechat-auto-publish——它把 wechat-formatter 和 wechat-publish 串成一条命令。
技术交流
扫码添加微信,交流使用问题、定制与合作:
项目赞助
本项目由微信公众号 「程序员白大力」 提供赞助,感谢支持:
License
MIT
Release files for opp-radar 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| opp_radar-1.0.1.tar.gz | 4.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| opp_radar-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.3 kB
Release files / opp_radar-1.0.1.tar.gz
| Download URL | opp_radar-1.0.1.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6658d51cf219320054fb2eb49d31f9bccaf216f865070500317c40d8aea54d54
|
|
BLAKE2b-256 checksum How to use checksums |
12a80135efbf54158afa16edcb826d4628b7dab62eb573c58fbdd6b8321eac9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 22, 2026.
Transparency logRelease files / opp_radar-1.0.1-py3-none-any.whl
| Download URL | opp_radar-1.0.1-py3-none-any.whl |
|---|---|
| Size | 4.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fbeb0325372d34a363306f6bb91aac9e4ad24ec161ed5bb35c55a0f569ff5509
|
|
BLAKE2b-256 checksum How to use checksums |
38d1bf2e3c66dafe1db833af3d57e2b30b571a043c4ad4918dfb3232b0a1c92e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 22, 2026.
Transparency log