Nothing stood out to me in the guide, the Pocket-IC regression is being worked on.
Thank you for the link to the example. I will try it out and compare it with my solution. My current issue is a public key verification error in the local development environment.
This (Pocket-IC regression) should be resolved after running icp network update.
This is due to the regression in pocket-ic
We added a test to catch this particular type of error next time and we’re discussing strategies to cover more component permutations when we release.
I’m currently working again on the new ICP CLI Internet Identity integration.
I noticed that with icp-cli ≥ 0.2.4 (currently using 0.2.7), the Internet Identity skill documentation recommends using the mainnet Internet Identity (https://id.ai/authorize) even for local development.
Does this mean that we no longer need to run a local Internet Identity canister during local development, and can instead directly use the mainnet II service together with PocketIC?
if you want you can do this, yes. pocket-ic meanwhile accepts mainnet signatures.
there is still a little discussion happening about what should be the primary advertised way as we are also updating examples as we speak.
I personally think that the local II setup creates serious friction for developers right now. especially if they regularly (re)start local networks and/or switch between different icp-cli projects.
so personally I am in favor of advertising the mainnet II usage in particular for newcomers unless local II usage significantly improves. I am curious on your thoughts on this 
Currently, I’m working on a new project that I’ve tried to finish several times in the past. This time, however, I’m taking a different approach: instead of working against the current, I’m trying to work with it.
What does that mean? I’m using the tooling and frameworks that the Internet Computer ecosystem currently favors, namely React (not Angular), Motoko and the provided Internet Identity integration. I’ve also been following the official AI skills and example’s and I have to say they work remarkably well.
Things simply started to stick together and I spent far less time fighting the stack and more time building the actual application.
Regarding the Internet Identity integration, I agree that the on-chain version works very well. However, I still prefer having a local Internet Identity instance during development.
Why? I like to keep my development environment completely separate from my real-world identities and accounts. Mixing development and production identities makes me somewhat uncomfortable. Call me paranoid if you like, but based on my experience, maintaining a strict separation between testing, development, and production environments has always been the safest approach.
This separation reduces the risk of accidental actions, protects production data and identities, and allows developers to experiment more freely. While using a local Internet Identity may introduce a few additional setup steps, I believe the benefits outweigh the inconvenience. Developers should still understand how their authentication stack works and be able to operate in a fully isolated development environment when needed.
For me, a 100% separated development, testing, and production setup was the safest way to work in the past, and I believe it will remain the safest approach in the future.
thanks for the detailed feedback 
that’s great to hear. however, some examples are still WIP in several ways:
- icp-cli support
- using latest libraries
- more tailored towards supporting the guides in the developer docs
- the https outcalls guide is already in quite good shape regarding this specifically
and if you encounter specific AI hallucinations when using the skills, feel free to open an issue. ideally you ask the agent in your session why it did things wrong and how a specific skill could be improved to avoid the mistake going forward.
I am not sure if we will change the internet-identity skill to advertise local usage by default, but you can always add your own instructions to the project that explicitly guide your agent to do so, independent of the ICP skills.