1 Commits

Author SHA1 Message Date
b462312c2e 项目说明 2026-04-24 09:38:45 +08:00
2 changed files with 107 additions and 12 deletions

65
ln_jq_app/CLAUDE.md Normal file
View File

@@ -0,0 +1,65 @@
# CLAUDE.md
Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-specific instructions as needed.
**Tradeoff:** These guidelines bias toward caution over speed. For trivial tasks, use judgment.
## 1. Think Before Coding
**Don't assume. Don't hide confusion. Surface tradeoffs.**
Before implementing:
- State your assumptions explicitly. If uncertain, ask.
- If multiple interpretations exist, present them - don't pick silently.
- If a simpler approach exists, say so. Push back when warranted.
- If something is unclear, stop. Name what's confusing. Ask.
## 2. Simplicity First
**Minimum code that solves the problem. Nothing speculative.**
- No features beyond what was asked.
- No abstractions for single-use code.
- No "flexibility" or "configurability" that wasn't requested.
- No error handling for impossible scenarios.
- If you write 200 lines and it could be 50, rewrite it.
Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
## 3. Surgical Changes
**Touch only what you must. Clean up only your own mess.**
When editing existing code:
- Don't "improve" adjacent code, comments, or formatting.
- Don't refactor things that aren't broken.
- Match existing style, even if you'd do it differently.
- If you notice unrelated dead code, mention it - don't delete it.
When your changes create orphans:
- Remove imports/variables/functions that YOUR changes made unused.
- Don't remove pre-existing dead code unless asked.
The test: Every changed line should trace directly to the user's request.
## 4. Goal-Driven Execution
**Define success criteria. Loop until verified.**
Transform tasks into verifiable goals:
- "Add validation" → "Write tests for invalid inputs, then make them pass"
- "Fix the bug" → "Write a test that reproduces it, then make it pass"
- "Refactor X" → "Ensure tests pass before and after"
For multi-step tasks, state a brief plan:
```
1. [Step] → verify: [check]
2. [Step] → verify: [check]
3. [Step] → verify: [check]
```
Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.
---
**These guidelines are working if:** fewer unnecessary changes in diffs, fewer rewrites due to overcomplication, and clarifying questions come before implementation rather than after mistakes.

View File

@@ -1,19 +1,49 @@
# ln_jq_app # 加氢预约app
### 主要功能介绍
1. 主要给本公司的合作司机提供加氢预约和路线规划的功能 方便日常预约加氢能源量
2. 主要给本公司的加氢站点提供预约查看功能,根据预约量准备和实际消耗数量
3. 主要核心流程
司机登录->无绑定记录需绑定车牌->绑定后即可提交预约(可选择修改预约时间、加氢量、站点)
站点登录->操作司机预约工单->确认或者拒绝->新预约单会有广播提醒->站点状态更改会广播提醒司机用户
4. 当前版本号1.2.5+8
sdk配置dart 3.9.0+
加氢预约app # 代码仓库说明
地址http://gitea.lnh2e.com/guyongliang/ln-ios.git
git tag 可查看所有已推送版本历史,都已做好标签
>生产测试分别对应不同的域名build的时候切换对应分支即可
origin/main 生产环境
origin/dev 测试环境
origin/dev_map 联调高德相关
# 项目结构介绍
1、登录页面分为司机端和站点端具体可以查看HomeController类中的getHomePage()函数,根据登录渠道的不同进入不同的菜单栏
2、全局搜索HttpService.to. 可以看到http相关设置、get post请求等
>lib/
├── common/ # 公共模块、项目配置
│ ├── styles/ # 样式配置
│ └── model/ # 数据模型
│ └──styles/theme.dart #域名切换功能配置、域名地址、相关key、主题色等
├── pages/ # 页面模块
│ ├── home/ # 跳转页面,区分跳转逻辑
│ ├── b_page/ # 站点端页面
│ ├── c_page/ # 司机端页面
│ └──base_widgets/NativePageIOS.dart #该类由原生android、ios 实现了高德相关功能
│ ├── login/ # 登录页面
│ ├── common/ # 公共页面
│ └── url_host/ # 域名切换功能页面
├── main.dart # 启动类
└── storage_service.dart # 缓存类存储枚举key
android jks
小羚羚
Ln123456.
高德key
安卓 92495660f7bc990cb475426c47c03b65
苹果:3ac08e5e14df9d7a52e98d40e21a0189
key:2cc1d822e313307fe311c3127a1deeb5
秘钥:0529b72df6bf0c577ff2182cb8b1d970
# 基本配置如下
安卓包名com.lingniu.driver 安卓包名com.lingniu.driver
iOS包名com.lnkj.ln_jq_app iOS包名com.lnkj.lnJqApp
>android jks别名密码
>小羚羚
>Ln123456.